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 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
accordingly.
Best Regards
Chaoyi Huang ( Joe Huang )
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Have you heard of this effort going on in multiple projects called
microversions? For example, in Nova:
http://docs.openstack.org/developer/nova/api_microversion_history.html
Nova and Ironic already support microversioned APIs. Cinder and Neutron
are working on it I think, and there could be others.
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
