Heh, so it turns out I totally forgot that Libcloud already defines a limited API for managing block storage:
* https://github.com/apache/libcloud/blob/trunk/libcloud/compute/base.py#L368 * https://github.com/apache/libcloud/blob/trunk/libcloud/compute/base.py#L705 Current block storage API is pretty tightly coupled to the compute API, but it's pretty similar to what Alex proposed so we can probably use it as a good starting point. Alex - what do you think? On Thu, Jun 27, 2013 at 12:16 AM, Alex Gaynor <[email protected]> wrote: > Hi all, > > I'm interested in adding block storage support to libcloud (for the > providers that suppor it of course). To that end, I've drawn up a simple > design for the driver and related classes for the features that seem to be > supported generally (I reviewed Rackspace and Amazon). > > You can find the design here: https://gist.github.com/alex/5872132, I > think > it's mostly self-explanatory and consistent with the rest of libcloud, as > well as the (thankfully consistent!) terminology used by the providers. > > Let me know what you think, and if there's general interest I'll go ahead > and start working on implementations for a few providers! > > Alex > > PS: In the interest of full disclosure, I work at Rackspace and have a > bunch of work time to help make libcloud awesome! > > > -- > "I disapprove of what you say, but I will defend to the death your right to > say it." -- Evelyn Beatrice Hall (summarizing Voltaire) > "The people's good is the highest law." -- Cicero > GPG Key fingerprint: 125F 5C67 DFE9 4084 >
