Re: [openstack-dev] [api][all] api variation release by release

2016-02-22 Thread Ian Cordasco
t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [api][all] api variation release by release > On 13 January 2016 at 14:28, Matt Riedemann wrote: > > On 1/13/2016 12:11 AM, joehuang wrote: > >> > >> Thanks for the information, it's good to know the docume

Re: [openstack-dev] [api][all] api variation release by release

2016-02-22 Thread John Garbutt
in each release. >> >> Best Regards >> Chaoyi Huang ( Joe Huang ) >> >> >> -Original Message- >> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] >> Sent: Wednesday, January 13, 2016 10:56 AM >> To: openstack-dev@lists.opens

Re: [openstack-dev] [api][all] api variation release by release

2016-01-13 Thread michael mccune
On 01/12/2016 09:55 PM, Matt Riedemann wrote: Nova and Ironic already support microversioned APIs. Cinder and Neutron are working on it I think, and there could be others. just as a heads up, sahara is also working towards implementing microversions in its next api[1] regards, mike [1]:

Re: [openstack-dev] [api][all] api variation release by release

2016-01-13 Thread Ken'ichi Ohmichi
Thanks for pointing the history out, Matt. According to this thread, I feel the NOTE of each release maximum microversion will help for users because many clouds are deployed from certain releases. https://review.openstack.org/#/c/267247/ is doing that. Thanks Ken Ohmichi 2016-01-13 11:55

Re: [openstack-dev] [api][all] api variation release by release

2016-01-13 Thread Matt Riedemann
, January 13, 2016 10:56 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [api][all] api variation release by release On 1/12/2016 7:27 PM, joehuang wrote: Hello, As more and more OpenStack release are deployed in the production cloud, multiple releases of OpenStack co-located

Re: [openstack-dev] [api][all] api variation release by release

2016-01-12 Thread joehuang
@lists.openstack.org Subject: Re: [openstack-dev] [api][all] api variation release by release On 1/12/2016 7:27 PM, joehuang wrote: > Hello, > > As more and more OpenStack release are deployed in the production > cloud, multiple releases of OpenStack co-located in a cloud is a ve

Re: [openstack-dev] [api][all] api variation release by release

2016-01-12 Thread Matt Riedemann
On 1/12/2016 7:27 PM, joehuang wrote: Hello, As more and more OpenStack release are deployed in the production cloud, multiple releases of OpenStack co-located in a cloud is a very common situation. For example, “Juno” and “Liberty” releases co-exist in the same cloud. Then the cloud

[openstack-dev] [api][all] api variation release by release

2016-01-12 Thread joehuang
Hello, As more and more OpenStack release are deployed in the production cloud, multiple releases of OpenStack co-located in a cloud is a very common situation. For example, "Juno" and "Liberty" releases co-exist in the same cloud. Then the cloud management software has to be aware of the API