Keystone does not report microversion headers

[Adam Young]

Keystone is now behind the other projects in reporting the microversions in the microversion header

[Nicolas Helgeson (nhelgeson)]

Is this bug requesting the addition of a feature to the keystone headers to make it print the OpenStack-API-Version similar to the cinder header?

example cinder header:
HTTP/1.1 300 Multiple Choices
Content-Type: application/json
Content-Length: 1122
Openstack-Api-Version: volume 3.0
Vary: OpenStack-API-Version
Date: Wed, 17 May 2017 18:47:57 GMT

[Adam Young (ayoung)]

Yes. THis bug was recorded during the summit session on microversions, and was based on the observation that, by not supporting microversions, Keystone makes it hard to evenly apply microversion-based client code across the openstack services

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/468189

[Lance Bragstad (lbragstad)]

The microversion discussion has come up several times, most recently in the keystone meeting today [0]. Let's table this fix until we know and understand where keystone stands, with respect to microversions. Otherwise it seems strange to report a microversion in the headers when we don't support it.

[0] http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2017-08-08.log.html#t2017-08-08T18:12:26

[Lance Bragstad (lbragstad)]

Colleen brought up a good point in office hours today about this [0]. If/when keystone supports microversions officially, this will be a hard requirement of that implementation. Otherwise it doesn't make a whole lot of sense to give the appearance that keystone supports microversions when it doesn't.

[0] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2017-12-05.log.html#t2017-12-05T19:57:37

[OpenStack Infra (hudson-openstack)]

Change abandoned by Nicolas Helgeson (<email address hidden>) on branch: master
Review: https://review.openstack.org/468189