We are making changes to v2 api only as v1 will be deprecated.
In addition to above analysis, as of now I have analyzed nova and cinder which is calling glanceclient.
In case of nova, it is using v1 version by default (except image-show can use v2 and v1 both) so even if request_ids list is passed from nova to glanceclient it will not break but it doesn't append request-id to the list as we are making changes to v2 only.
Similarly in case of cinder, service provider can configure (glance_api_version) which api version of glance should be used and in case of v1 it will not append request-id to request-ids list.
So should we make changes to v1 api as well so that it will return request-ids in case v1 api is used?
Please suggest.
Hi Stuart, Erno
We are making changes to v2 api only as v1 will be deprecated.
In addition to above analysis, as of now I have analyzed nova and cinder which is calling glanceclient.
In case of nova, it is using v1 version by default (except image-show can use v2 and v1 both) so even if request_ids list is passed from nova to glanceclient it will not break but it doesn't append request-id to the list as we are making changes to v2 only.
Similarly in case of cinder, service provider can configure (glance_ api_version) which api version of glance should be used and in case of v1 it will not append request-id to request-ids list.
So should we make changes to v1 api as well so that it will return request-ids in case v1 api is used?
Please suggest.