Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 1:16 PM, Brant Knudson wrote: > This is pretty much the same as your example of specifying a different > version for the nova API on different requests (except they have a lot more > than just 2 and 3). We also keep adding routes to v3 each release, so what

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 1:04 PM, Dean Troyer wrote: > > > On Tue, Feb 16, 2016 at 12:17 PM, Sean Dague wrote: > >> Honestly, doing per API call version switching is probably going to end >> in tears. HTTP is stateless, so it's allowed, but it will end in tears

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 12:17 PM, Sean Dague wrote: > Honestly, doing per API call version switching is probably going to end > in tears. HTTP is stateless, so it's allowed, but it will end in tears > of complexity as you need to self modify resources before passing them > back.

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On 02/16/2016 01:13 PM, Dean Troyer wrote: > On Tue, Feb 16, 2016 at 8:34 AM, Andrew Laski > wrote: > ... > > It's easy enough to think that users will just read the docs and > carefully consider every version increment that they want to

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 8:34 AM, Andrew Laski wrote: ... > It's easy enough to think that users will just read the docs and > carefully consider every version increment that they want to consume but > when they've been on version 2.7 for a while and a new thing comes out in >

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Excerpts from Andrew Laski's message of 2016-02-16 06:34:53 -0800: > > On Tue, Feb 16, 2016, at 07:54 AM, Alex Xu wrote: > > > > > > 2016-02-16 19:53 GMT+08:00 Sean Dague : > >> On 02/12/2016 03:55 PM, Andrew Laski wrote: > >> > > Starting a new thread to continue a thought that

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On 02/16/2016 09:34 AM, Andrew Laski wrote: > > > > On Tue, Feb 16, 2016, at 07:54 AM, Alex Xu wrote: >> >> >> 2016-02-16 19:53 GMT+08:00 Sean Dague > >: >> >> On 02/12/2016 03:55 PM, Andrew Laski wrote: >> > Starting a new thread to

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016, at 07:54 AM, Alex Xu wrote: > > > 2016-02-16 19:53 GMT+08:00 Sean Dague : >> On 02/12/2016 03:55 PM, Andrew Laski wrote: >> > Starting a new thread to continue a thought that came up in >> >

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 13:01, Sean Dague a écrit : On 02/16/2016 03:33 AM, Sylvain Bauza wrote: Le 16/02/2016 09:30, Sylvain Bauza a écrit : Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN >: Regards

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

2016-02-16 19:53 GMT+08:00 Sean Dague : > On 02/12/2016 03:55 PM, Andrew Laski wrote: > > Starting a new thread to continue a thought that came up in > > > http://lists.openstack.org/pipermail/openstack-dev/2016-February/086457.html > . > > The Nova API microversion framework

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On 02/16/2016 03:33 AM, Sylvain Bauza wrote: > > > Le 16/02/2016 09:30, Sylvain Bauza a écrit : >> >> >> Le 16/02/2016 04:09, Alex Xu a écrit : >>> >>> >>> 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN >> >: >>> >>> Regards >>>

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On 02/12/2016 03:55 PM, Andrew Laski wrote: > Starting a new thread to continue a thought that came up in > http://lists.openstack.org/pipermail/openstack-dev/2016-February/086457.html. > The Nova API microversion framework allows for backwards compatible and > backwards incompatible changes but

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 09:30, Sylvain Bauza a écrit : Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN >: Regards Ghanshyam Mann On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Le 16/02/2016 04:09, Alex Xu a écrit : 2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN >: Regards Ghanshyam Mann On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu > wrote: > If we

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

2016-02-16 9:47 GMT+08:00 GHANSHYAM MANN : > Regards > Ghanshyam Mann > > > On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu wrote: > > If we support 2.x.y, when we bump 'x' is a problem. We didn't order the > API > > changes for now, the version of API change

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Regards Ghanshyam Mann On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu wrote: > If we support 2.x.y, when we bump 'x' is a problem. We didn't order the API > changes for now, the version of API change is just based on the order of > patch merge. For support 2.x.y, we need bump 'y'

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

If we support 2.x.y, when we bump 'x' is a problem. We didn't order the API changes for now, the version of API change is just based on the order of patch merge. For support 2.x.y, we need bump 'y' first for back-compatible changes I guess. As I remember, we said before, the new feature is the

[openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

Starting a new thread to continue a thought that came up in http://lists.openstack.org/pipermail/openstack-dev/2016-February/086457.html. The Nova API microversion framework allows for backwards compatible and backwards incompatible changes but there is no way to programmatically distinguish the