<div dir="ltr">Recapping... <div><br></div><div>- ensure we are not using X- in the header</div><div>- use the service type, not name</div><div><br></div><div>For keystone it would be: <span style="font-size:12.8px">OpenStack-API-Version: identity 3.7</span></div><div><span style="font-size:12.8px">For nova it would be: OpenStack-API-Version: compute 2.27</span></div><div><span style="font-size:12.8px"> (which matches what is proposed here: <a href="https://review.openstack.org/#/c/300077/14/api-guide/source/microversions.rst">https://review.openstack.org/#/c/300077/14/api-guide/source/microversions.rst</a>) </span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Similarly for manila and ironic, I don't have the links handy, or the what the headers are currently</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jun 18, 2016 at 11:13 AM, Ravi, Goutham <span dir="ltr"><<a href="mailto:Goutham.Ravi@netapp.com" target="_blank">Goutham.Ravi@netapp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">True, manila is currently using the same header; but given that nova and ironic are supporting the new header recommendation, this has come up for discussion in the manila community.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">In any case, the use of the prefix “X-“, and project names within the header is not recommended. Please refer to the API Working Group’s recommendation in this regard:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><a href="http://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html" target="_blank">http://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">The example already suggests what needs to be done in case of the identity project
</span><span style="font-size:11.0pt;font-family:Wingdings">J</span><span style="font-size:11.0pt;font-family:Calibri"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">--<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Goutham<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Steve Martinelli <<a href="mailto:s.martinelli@gmail.com" target="_blank">s.martinelli@gmail.com</a>><br>
<b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<b>Date: </b>Saturday, June 18, 2016 at 6:22 AM<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<b>Subject: </b>Re: [openstack-dev] Version header for OpenStack microversion support<u></u><u></u></span></p>
</div><div><div class="h5">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p>Looks like Manila is using the service name instead of type (X-OpenStack-Manila-API-Version) according to this link anyway:
<a href="http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html" target="_blank">
http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html</a><u></u><u></u></p>
<p>Keystone can follow the cross project spec and use the service type (Identity instead of Keystone).
<u></u><u></u></p>
<div>
<p class="MsoNormal">On Jun 17, 2016 12:44 PM, "Ed Leafe" <<a href="mailto:ed@leafe.com" target="_blank">ed@leafe.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">On Jun 17, 2016, at 11:29 AM, Henry Nash <<a href="mailto:henrynash9@mac.com" target="_blank">henrynash9@mac.com</a>> wrote:<br>
<br>
> 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" target="_blank">http://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html</a>).<br>
><br>
> One thing I noticed was that the header specified in this spec is of the form:<br>
><br>
> OpenStack-API-Version: [SERVICE_TYPE] [X,Y]<br>
><br>
> for example:<br>
><br>
> OpenStack-API-Version: identity 3.7<br>
><br>
> 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.<br>
><br>
> X-OpenStack-Nova-API-Version: 2.12<br>
><br>
> 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.<span style="font-family:MingLiU"><br>
<br>
</span>Yes, the plan is to converge on the more generic headers. The Nova headers (don’t know about Manilla) pre-date the API WG spec, and were the motivation for development of that spec. We’ve even made it possible to accept both header formats [0] until
things can be migrated to the recommended format.<span style="font-family:MingLiU"><br>
<br>
</span>[0] <a href="https://review.openstack.org/#/c/300077/" target="_blank">https://review.openstack.org/#/c/300077/</a><br>
<br>
-- Ed Leafe<br>
<br>
<br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</div></div></div>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>