Mailing-List: contact libcloud-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: libcloud@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of grig.gheorghiu@gmail.com
 designates 209.85.216.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=EmG5qhwV0L+mVDw9t5dpe+3/iUf2GhnEOl9QXpBily1vlBkxii+d02EOldY2ddh7mF
         yPdawVQpX3BOGhuT0ixbWqkbVuEp1swXm/D8xx5+X2ADze5Tg9fbk5giCsBNSncD6YX/
         l8YC2woRFMiJiYW/BCS/Yr5Ja1WFGO6i1e/O0=
MIME-Version: 1.0
In-Reply-To: <5DCD0C08-5890-4FBA-A507-B7168C510856@gmail.com>
References: <AANLkTi=Y1B+qQzJGwA2ns4ks9kyZpu3EzzOscXbXEMYk@mail.gmail.com>
	<5DCD0C08-5890-4FBA-A507-B7168C510856@gmail.com>
Date: Thu, 4 Nov 2010 15:16:46 -0700
Message-ID: <AANLkTi=S7Y8EB+PFjn=W-vjw5+e6hPi1Y_c1KLYHunkg@mail.gmail.com>
From: Grig Gheorghiu <grig.gheorghiu@gmail.com>
To: libcloud@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [libcloud] Cloud storage providers/drivers

On Thu, Nov 4, 2010 at 2:48 PM, Eric Woods <woodstae@gmail.com> wrote:
> Hi Grig,
>
> We did address this in libcloud's Java initiative. =A0After implementing =
a Java port of libcloud, we pulled SimpleCloud under the libcloud umbrella =
to provide storage, queue, and table services. =A0Following the libcloud de=
sign patterns, we've implemented working adapters for Amazon S3 and Nirvani=
x. =A0Rackspace has also expressed interest in contributing an adapter for =
CloudFiles. =A0Take a look at the Java repository for the implementation: =
=A0https://svn.apache.org/repos/asf/incubator/libcloud/sandbox/java/trunk/s=
rc/simplecloud/storage
>
> I think this would be great in the python base, too.
>

Thanks for the pointers to the Java code.

So how would you envision adding storage providers to the python
codebase? Would there be a simplecloud directory under the top
libcloud directory, in parallel with the libcloud directory which
contains base.py? So something like:

libcloud/
        libcloud/
                base.py
                providers.py
                drivers/
        simplecloud/
                storage/
                       base.py
                       providers.py
                       drivers/

....and then you would define the base storage classes similarly to
the Java interfaces in simplecloud/storage/base.py, and the actual
implementations in drivers/S3.py.

Would this make sense?

Grig