Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-08 Thread Ghanshyam Mann
> -Original Message- > From: Andrew Laski [mailto:and...@lascii.com] > Sent: 04 August 2016 22:18 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] Some thoughts on API microversions > > > > On Thu, Aug 4, 2016, at 08:20 AM, Sea

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-08 Thread Chris Dent
On Wed, 3 Aug 2016, Andrew Laski wrote: I am a fan of microversions. I think they work wonderfully to express when a resource representation changes, or when different data is required in a request. This allows clients to make the same request across multiple clouds and expect the exact same

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-06 Thread Matt Riedemann
On 8/3/2016 7:54 PM, Andrew Laski wrote: I've brought some of these thoughts up a few times in conversations where the Nova team is trying to decide if a particular change warrants a microversion. I'm sure I've annoyed some people by this point because it wasn't germane to those discussions. So

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-05 Thread Jim Rollenhagen
On Wed, Aug 03, 2016 at 08:54:07PM -0400, Andrew Laski wrote: > I've brought some of these thoughts up a few times in conversations > where the Nova team is trying to decide if a particular change warrants > a microversion. I'm sure I've annoyed some people by this point because > it wasn't

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-05 Thread Jim Rollenhagen
On Thu, Aug 04, 2016 at 04:31:00PM -0400, Jay Pipes wrote: > On 08/04/2016 01:17 PM, Chris Friesen wrote: > >On 08/04/2016 09:28 AM, Edward Leafe wrote: > > > >>The idea that by specifying a distinct microversion would somehow > >>guarantee > >>an immutable behavior, though, is simply not the

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-05 Thread Alex Xu
2016-08-05 0:43 GMT+08:00 Andrew Laski : > > > On Thu, Aug 4, 2016, at 11:40 AM, John Garbutt wrote: > > On 4 August 2016 at 16:28, Edward Leafe wrote: > > > On Aug 4, 2016, at 8:18 AM, Andrew Laski wrote: > > > > > >> This gets to the point

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread Jay Pipes
On 08/04/2016 01:17 PM, Chris Friesen wrote: On 08/04/2016 09:28 AM, Edward Leafe wrote: The idea that by specifying a distinct microversion would somehow guarantee an immutable behavior, though, is simply not the case. We discussed this at length at the midcycle regarding the dropping of the

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread Sean Dague
On 08/04/2016 12:47 PM, John Garbutt wrote: > On 4 August 2016 at 14:18, Andrew Laski wrote: >> On Thu, Aug 4, 2016, at 08:20 AM, Sean Dague wrote: >>> On 08/03/2016 08:54 PM, Andrew Laski wrote: I've brought some of these thoughts up a few times in conversations

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread Ed Leafe
On Aug 4, 2016, at 12:17 PM, Chris Friesen wrote: >> The idea that by specifying a distinct microversion would somehow guarantee >> an immutable behavior, though, is simply not the case. We discussed this at >> length at the midcycle regarding the dropping of the

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread Chris Friesen
On 08/04/2016 09:28 AM, Edward Leafe wrote: The idea that by specifying a distinct microversion would somehow guarantee an immutable behavior, though, is simply not the case. We discussed this at length at the midcycle regarding the dropping of the nova-network code; once that's dropped, there

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread John Garbutt
On 4 August 2016 at 14:18, Andrew Laski wrote: > On Thu, Aug 4, 2016, at 08:20 AM, Sean Dague wrote: >> On 08/03/2016 08:54 PM, Andrew Laski wrote: >> > I've brought some of these thoughts up a few times in conversations >> > where the Nova team is trying to decide if a

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread Andrew Laski
On Thu, Aug 4, 2016, at 11:40 AM, John Garbutt wrote: > On 4 August 2016 at 16:28, Edward Leafe wrote: > > On Aug 4, 2016, at 8:18 AM, Andrew Laski wrote: > > > >> This gets to the point I'm trying to make. We don't guarantee old > >> behavior in all cases at

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread John Garbutt
On 4 August 2016 at 16:28, Edward Leafe wrote: > On Aug 4, 2016, at 8:18 AM, Andrew Laski wrote: > >> This gets to the point I'm trying to make. We don't guarantee old >> behavior in all cases at which point users can no longer rely on >> microversions to

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread Edward Leafe
On Aug 4, 2016, at 8:18 AM, Andrew Laski wrote: > This gets to the point I'm trying to make. We don't guarantee old > behavior in all cases at which point users can no longer rely on > microversions to signal non breaking changes. And where we do guarantee > old behavior

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread Andrew Laski
On Thu, Aug 4, 2016, at 08:20 AM, Sean Dague wrote: > On 08/03/2016 08:54 PM, Andrew Laski wrote: > > I've brought some of these thoughts up a few times in conversations > > where the Nova team is trying to decide if a particular change warrants > > a microversion. I'm sure I've annoyed some

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-04 Thread Sean Dague
On 08/03/2016 08:54 PM, Andrew Laski wrote: > I've brought some of these thoughts up a few times in conversations > where the Nova team is trying to decide if a particular change warrants > a microversion. I'm sure I've annoyed some people by this point because > it wasn't germane to those

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-03 Thread Alex Xu
Agree with Andrew about Microversions may overused. I thought similar thing before. The Microversions should be the version control of API 'core' protocol. So I can say the protocol of send an action to server is: 'POST /servers/{uuid}/action'. We won't bump microversion for any new action or

[openstack-dev] [Nova] Some thoughts on API microversions

2016-08-03 Thread Andrew Laski
I've brought some of these thoughts up a few times in conversations where the Nova team is trying to decide if a particular change warrants a microversion. I'm sure I've annoyed some people by this point because it wasn't germane to those discussions. So I'll lay this out in it's own thread. I am