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 as a community, then we promote it into core if/when it is ready. The thing I don't like about the extension promotion process is that it breaks clients when the volume API is promoted. But I'm all for trying it and seeing what happens. Justin On Tue, Mar 22, 2011 at 1:20 PM, Jay Pipes <[email protected]> wrote: > On Tue, Mar 22, 2011 at 3:21 PM, Justin Santa Barbara > <[email protected]> wrote: > > So: When can we expect volume support in nova? If I repackaged my > volumes > > API as an extension, can we get it merged into Cactus? > > I would personally support this. > > Wasn't one of the ideas of the extensions API to provide a bit of a > playground for features to bake that, at some future time, be made a > core resource endpoint in the OpenStack API? This would be a perfect > example of that, no? > > -jay >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
