[openstack-dev] [python-novaclient][nova] future of --os-compute-api-version option and whole api versioning
akurilin at mirantis.com
Fri Jan 30 17:39:40 UTC 2015
Thanks for the answer. Can I help with implementation of novaclient part?
On Wed, Jan 28, 2015 at 11:50 AM, Christopher Yeoh <cbkyeoh at gmail.com>
> On Fri, 23 Jan 2015 15:51:54 +0200
> Andrey Kurilin <akurilin at mirantis.com> wrote:
> > Hi everyone!
> > After removing nova V3 API from novaclient, implementation of v1.1
> > client is used for v1.1, v2 and v3 .
> > Since we moving to micro versions, I wonder, do we need such
> > mechanism of choosing api version(os-compute-api-version) or we can
> > simply remove it, like in proposed change - ?
> > If we remove it, how micro version should be selected?
> So since v3 was never officially released I think we can re-use
> os-compute-api-version for microversions which will map to the
> X-OpenStack-Compute-API-Version header. See here for details on what
> the header will look like. We need to also modify novaclient to handle
> errors when a version requested is not supported by the server.
> If the user does not specify a version number then we should not send
> anything at all. The server will run the default behaviour which for
> quite a while will just be v2.1 (functionally equivalent to v.2)
> >  - https://review.openstack.org/#/c/138694
> >  -
> >  - https://review.openstack.org/#/c/149006
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev