incubator-libcloud mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Woods <>
Subject Re: [libcloud] Cloud storage providers/drivers
Date Mon, 15 Nov 2010 15:31:33 GMT
Hi Grig,

I found that the authentication code was the most difficult to port, especially for AWS. 
Java and Python have very different utilities for handling encoding/encryption schemes, so
most of my authentication code was written from scratch.  By all means, do what makes the
most sense for Python.

I expect that the factoring of common components (e.g. connections), libcloud components (e.g.
Node), and storage components (e.g. Item) and general design patterns are what can be leveraged
most from the Java work.  As you dive into this, please feel free to ask questions and provide
feedback on the Java structure.


On Nov 14, 2010, at 5:15 PM, Grig Gheorghiu wrote:

> Quick update: I've been trying to port the Java code from
> simplecloud/storage but I've had mixed success. I am tempted to start
> from scratch and use the Python code from the sample S3 code published
> by Amazon here:
> . The
> license is 'new BSD'. Would it be appropriate to base the libcloud S3
> driver on that code and license? I would like to at least use the
> authentication code from that sample.
> Grig
> On Thu, Nov 4, 2010 at 6:01 PM, Grig Gheorghiu <> wrote:
>> On Thu, Nov 4, 2010 at 5:57 PM, Tom Davis <> wrote:
>>> I like this structure, too. +1
>> One thing with the refactoring of the directory structure is that
>> tools that expect to import libcloud modules in a certain way might
>> break. Not sure if that is a big concern or not.
>>> I am also intrigued by Grig's DASH idea!
>> Glad to hear that ;-) Hopefully it will graduate from the 'dream'
>> stage to some sort of implementation ;-)
>> Grig

View raw message