[openstack-dev] [api][all] api variation release by release
ken1ohmichi at gmail.com
Thu Jan 14 00:40:33 UTC 2016
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
https://review.openstack.org/#/c/267247/ is doing that.
2016-01-13 11:55 GMT+09:00 Matt Riedemann <mriedem at linux.vnet.ibm.com>:
> On 1/12/2016 7:27 PM, joehuang wrote:
>> 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 variation
>> of different releases, and deal with the different field of object in
>> the request / response. For example, in “Juno”, no “multiattach” field
>> in the “volume” object, but the field presents in “Liberty”.
>> Each releases will bring some API changes, it will be very useful that
>> the API variation will also be publish after each release is delivered,
>> so that the cloud management software can read and changes and react
>> Best Regards
>> Chaoyi Huang ( Joe Huang )
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Have you heard of this effort going on in multiple projects called
> microversions? For example, in Nova:
> Nova and Ironic already support microversioned APIs. Cinder and Neutron are
> working on it I think, and there could be others.
> Matt Riedemann
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev