[openstack-dev] [nova] Nova v3 API work
doug.hellmann at dreamhost.com
Wed Apr 24 02:24:31 UTC 2013
On Tue, Apr 23, 2013 at 6:22 PM, Russell Bryant <rbryant at redhat.com> wrote:
> On 04/23/2013 07:34 PM, Doug Hellmann wrote:
> > On Mon, Apr 22, 2013 at 10:33 AM, Christopher Yeoh <cyeoh at au1.ibm.com
> > <mailto:cyeoh at au1.ibm.com>> wrote:
> > Hi Russell,
> > The following are the blueprints I've created based on the Nova V3
> > discussions. As requested I've split them into multiple blueprints to
> > make working out when we've actually finished parts of the V3 API
> > easier.
> > https://blueprints.launchpad.net/nova/+spec/nova-v3-api-filter
> > https://blueprints.launchpad.net/nova/+spec/v3-api-cleanup-misc
> > https://blueprints.launchpad.net/nova/+spec/v3-api-expected-errors
> > https://blueprints.launchpad.net/nova/+spec/v3-api-inconsistencies
> > https://blueprints.launchpad.net/nova/+spec/v3-api-return-codes
> > https://blueprints.launchpad.net/nova/+spec/v3-multi-status-support
> > The following is the blueprint for the new API Extension framework
> > There is an initial WIP patch for the barebones bits of the framework
> > here:
> > https://review.openstack.org/#/c/27276/
> > Regards,
> > Chris
> > If there are plans to build a new API anyway, would it make sense to
> > look at Pecan/WSME for nova at the same time as the other projects that
> > were going to investigate it during this release cycle?
> I would like to see this seriously considered. I also understand that
> it's more work and those driving the v3 API want to make sure it gets
> completed. What do you guys think? How much extra work would this be?
> Would recruiting someone else to help make it manageable?
I'm available to at least offer advice about getting started, debugging,
and code reviews. I should have some cycles for coding in a few weeks, too.
> Russell Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev