Now that I have had a chance to look into this a little more, I realize
that I had missed the connection of talking about the volume functionality
missing in the Openstack Rest API (versus the EC2 api that was already
there).
Justin: Sorry I'm a bit late to the game on this, but is there a
I know that creiht is looking at this for Rackspace. Chuck, anything to add
to this discussion?
John
-Original Message-
From: openstack-bounces+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Adam Johnson
Sent: Monday,
I am happy to do a first pass over the volume API. I can do it as an
extension or not, whatever is more likely to be merged.
My personal feeling is that we shouldn't use extensions for something this
core, but we can do a 'full lifecycle' if we want: I'll write it as an
extension, we work on it
Describing full Volume API as an extension may work in the short term. Long
term though we're moving towards having a suite of APIs. From this perspective
adding an extension to OpenStack Compute API seems a little strange to me. But
it could work short term, my concern is that we should
On Mar 22, 2011, at 3:33 PM, Justin Santa Barbara wrote:
The thing I don't like about the extension promotion process is that it
breaks clients when the volume API is promoted
Promotion only occurs between version changes in the API, that is when we're
moving from say 1.1 to 2.0. Version
Hey Chuck,
Thanks for the response. We are very interested in this project as
well, and may want to contribute. We're currently evaluating options
such as Sheepdog and others to see if they fit the bill. In order to
fully evaluate these options, it would be great to have *some* API
support in
Hey Adam,
As far as I understand it, there is already basic volume support within
nova, and that there are currently some suggested changes for the current
API. We are planning to fit within that API as much as possible, and work
with the community to make any changes that may need to be made
Sounds great,
We are basing our developments off of Justin's API work, just wanted
to get a consensus from the community on his approach, and see how we
can get it in as an optional component so that people can start
getting their hands dirty.
We're also interested in the snapshots support as
8 matches
Mail list logo
