
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi<div class=""><br class=""></div><div class="">We are currently in the process of implementing microversion support in keystone - and are obviously trying to follow the cross-projec spec for this (<a href="http://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html" class="">http://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html</a>). </div><div class=""><br class=""></div><div class="">One thing I noticed was that the header specified in this spec is of the form:</div><div class=""><br class=""></div><div class="">OpenStack-API-Version: [SERVICE_TYPE] [X,Y]</div><div class=""><br class=""></div><div class="">for example:</div><div class=""><br class=""></div><div class="">OpenStack-API-Version: identity 3.7</div><div class=""><br class=""></div><div class="">However, from what i can see of the current implementations I have seen of microversioning in OpenStack (Nova, Manilla), they use service-specific headers, e.g.</div><div class=""><br class=""></div><div class="">X-OpenStack-Nova-API-Version: 2.12</div><div class=""><br class=""></div><div class="">My question is whether there a plan to converge on the generalized header format….or are we keep with the service-specific headers? I’d obviously like to implement the correct one for keystone.</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Henry</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>