Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 Thread GHANSHYAM MANN
On Thu, Mar 31, 2016 at 4:47 AM, Matthew Treinish wrote: > On Wed, Mar 30, 2016 at 03:26:13PM -0400, Sean Dague wrote: >> During the Nova API meeting we had some conversations about priorities, >> but this feels like the thing where a mailing list conversation is more >>

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 Thread Ken'ichi Ohmichi
2016-03-30 12:54 GMT-07:00 Matt Riedemann : >>> - Microversion Testing in Tempest (underway) > > How much coverage do we have today? This could be like novaclient where > people just start hacking on adding tests for each microversion (assuming > gmann would be working

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 Thread Ken'ichi Ohmichi
2016-03-30 12:26 GMT-07:00 Sean Dague : > > One other issue that we've been blocking on for a while has been > Capabilities discovery. Some API proposed adds like live resize have > been conceptually blocked behind this one. Once upon a time there was a > theory that JSON Home was

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 Thread Alex Xu
2016-03-31 19:21 GMT+08:00 Sean Dague : > On 03/31/2016 04:55 AM, Alex Xu wrote: > > > > > > 2016-03-31 5:36 GMT+08:00 Matt Riedemann > > As discussed in IRC today, first steps (I think) are removing the > > deprecated 'osapi_v21.enabled'

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 Thread Sean Dague
On 03/31/2016 04:55 AM, Alex Xu wrote: > > > 2016-03-31 5:36 GMT+08:00 Matt Riedemann As discussed in IRC today, first steps (I think) are removing the > deprecated 'osapi_v21.enabled' option in newton so v2.1 can't be > disabled. > > And we need

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 Thread Sean Dague
On 03/30/2016 05:27 PM, Andrew Laski wrote: > > > On Wed, Mar 30, 2016, at 04:47 PM, Adam Young wrote: >> On 03/30/2016 04:16 PM, Andrew Laski wrote: >>> >>> On Wed, Mar 30, 2016, at 03:54 PM, Matt Riedemann wrote: On 3/30/2016 2:42 PM, Andrew Laski wrote: > > On Wed, Mar 30,

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 Thread Chris Dent
On Wed, 30 Mar 2016, Matt Riedemann wrote: - POC of Gabbi for additional API validation I'm assuming cdent would be driving this, and he's also working on the resource providers stuff for the scheduler, but might be a decent side project for him to stay sane. As Jay points out Sergey

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 Thread Alex Xu
2016-03-31 5:36 GMT+08:00 Matt Riedemann : > > > On 3/30/2016 2:26 PM, Sean Dague wrote: > >> During the Nova API meeting we had some conversations about priorities, >> but this feels like the thing where a mailing list conversation is more >> inclusive to get

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Matt Riedemann
On 3/30/2016 2:26 PM, Sean Dague wrote: During the Nova API meeting we had some conversations about priorities, but this feels like the thing where a mailing list conversation is more inclusive to get agreement on things. I think we need to remain focused on what API related work will have the

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Andrew Laski
On Wed, Mar 30, 2016, at 04:47 PM, Adam Young wrote: > On 03/30/2016 04:16 PM, Andrew Laski wrote: > > > > On Wed, Mar 30, 2016, at 03:54 PM, Matt Riedemann wrote: > >> > >> On 3/30/2016 2:42 PM, Andrew Laski wrote: > >>> > >>> On Wed, Mar 30, 2016, at 03:26 PM, Sean Dague wrote: > During

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Adam Young
On 03/30/2016 04:16 PM, Andrew Laski wrote: On Wed, Mar 30, 2016, at 03:54 PM, Matt Riedemann wrote: On 3/30/2016 2:42 PM, Andrew Laski wrote: On Wed, Mar 30, 2016, at 03:26 PM, Sean Dague wrote: During the Nova API meeting we had some conversations about priorities, but this feels like

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Sean Dague
On 03/30/2016 04:17 PM, Jay Pipes wrote: > On 03/30/2016 12:54 PM, Matt Riedemann wrote: - POC of Gabbi for additional API validation >> >> I'm assuming cdent would be driving this, and he's also working on the >> resource providers stuff for the scheduler, but might be a decent side >>

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Andrew Laski
On Wed, Mar 30, 2016, at 03:54 PM, Matt Riedemann wrote: > > > On 3/30/2016 2:42 PM, Andrew Laski wrote: > > > > > > On Wed, Mar 30, 2016, at 03:26 PM, Sean Dague wrote: > >> During the Nova API meeting we had some conversations about priorities, > >> but this feels like the thing where a

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Jay Pipes
On 03/30/2016 12:54 PM, Matt Riedemann wrote: - POC of Gabbi for additional API validation I'm assuming cdent would be driving this, and he's also working on the resource providers stuff for the scheduler, but might be a decent side project for him to stay sane. Actually, Sergey Nikitin can

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Matt Riedemann
On 3/30/2016 2:42 PM, Andrew Laski wrote: On Wed, Mar 30, 2016, at 03:26 PM, Sean Dague wrote: During the Nova API meeting we had some conversations about priorities, but this feels like the thing where a mailing list conversation is more inclusive to get agreement on things. I think we

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Matthew Treinish
On Wed, Mar 30, 2016 at 03:26:13PM -0400, Sean Dague wrote: > During the Nova API meeting we had some conversations about priorities, > but this feels like the thing where a mailing list conversation is more > inclusive to get agreement on things. I think we need to remain focused > on what API

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 Thread Andrew Laski
On Wed, Mar 30, 2016, at 03:26 PM, Sean Dague wrote: > During the Nova API meeting we had some conversations about priorities, > but this feels like the thing where a mailing list conversation is more > inclusive to get agreement on things. I think we need to remain focused > on what API related