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 really be thinking of Volumes as a core API, not additional features to Compute. Certainly we may need to extend compute to do things like mount/unmount a volume.
-jOrGe W. On Mar 22, 2011, at 3:20 PM, Jay Pipes wrote: > On Tue, Mar 22, 2011 at 3:21 PM, Justin Santa Barbara > <jus...@fathomdb.com> 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 : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp