<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 3, 2014 at 10:20 AM, Waines, Greg <span dir="ltr"><<a href="mailto:Greg.Waines@windriver.com" target="_blank">Greg.Waines@windriver.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thanks Anne.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">But the individual APIs, say Compute API, are not up-versioned every OpenStack Release.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">However the individual APIs, say Compute API V2, (I believe) are extended every OpenStack Release … possibly new requests, possibly new parameters for requests,
possibly new attributes in responses.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> </span></p></div></div></blockquote><div><br></div><div>Yes, this is correct, extension only happens in extensions though for v2. I cannot say v2 itself changes, it does not. Extensions may be added or removed however. A cloud provider then choses what to put into production for their customers.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">So there are going to be IceHouse(say)-specific changes in (say) Compute API V2 … correct ?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> </span></p></div></div></blockquote><div><br></div><div>Yes. Those are mostly tracked with blueprints if you want to know what actually changed in a given release, such as: <a href="https://blueprints.launchpad.net/nova/icehouse">https://blueprints.launchpad.net/nova/icehouse</a> </div>
<div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple">
<div><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">But it sounds like there is no tag or commit that represents an ‘up-to-Havana only’ version of Compute API V2 … correct ?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> </span></p></div></div></blockquote><div><br></div><div>Not for the docs. I've been trying to figure out how you could figure it out from the code itself but not really finding a way even after reading lots of specs about microversions.</div>
<div><br></div><div>The API docs also are not complete any given release, sad to say. The mechanism for adding a new extension should include a "DocImpact" flag in the commit, which then adds a doc bug automatically. I know we try to quantify and track -- there are 32 bugs outstanding for Compute API for example:</div>
<div><br></div><div><a href="https://bugs.launchpad.net/openstack-api-site/+bugs/?field.tag=nova">https://bugs.launchpad.net/openstack-api-site/+bugs/?field.tag=nova</a><br></div><div><br></div><div>If you have ideas for how we can improve, I'd be happy to hear them. We didn't get traction on a "registry" idea back in 2012. We also haven't seen much compliance on doc requirements on extensions themselves. It's certainly a worthwhile pursuit, but mostly the cloud providers are documenting their own clouds. OpenStack upstream should document the standard more than the release is my current thinking.</div>
<div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple">
<div><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Greg.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"> <a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a> [mailto:<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>]
<b>On Behalf Of </b>Anne Gentle<br>
<b>Sent:</b> Tuesday, September 02, 2014 11:36 PM<br>
<b>To:</b> Waines, Greg<br>
<b>Cc:</b> <a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.openstack.org</a><br>
<b>Subject:</b> Re: [Openstack-docs] 2013.2 tag seems broken ?<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<blockquote style="border-style:none none none solid;border-left-color:rgb(204,204,204);border-left-width:1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p><span style="color:rgb(31,73,125)">< SNIP ><u></u><u></u></span></p>
<p><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
</div>
</div>
</blockquote><div class="">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We have had this discussion in the past, read it at <a href="http://lists.openstack.org/pipermail/openstack-docs/2014-April/004337.html" target="_blank">
http://lists.openstack.org/pipermail/openstack-docs/2014-April/004337.html</a>. The basic problem with tagging API docs is that there's not a map from say, havana, to API versions. The deployers choices for that particular release would look something like
this:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Block Storage API v1 or v2<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Compute API v2<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Identity API v2.0 or v3<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Image Service v1, v1.1, or v2<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">(not Database service, they weren't integrated then)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Networking API v2.0<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Object Storage v1<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Orchestration v1<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Telemetry v2<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">So I think there are 3*2*3*4*2*2*2*2 = 1152 possibilities of combining API versions a cloud provider offers for Havana, where you can choose not to deploy an API endpoint at all. We can't dictate to the provider "you must run these API
versions when running havana" so I've avoided tagging the docs for overhead and maintenance and explanatory reasons. :) <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Hopefully these explanations makes sense to you, sounds like you've guessed right all along. I certainly want our docs to be re-used and they're licensed completely for re-use, but I'm pretty sure I can't accurately say which API calls
go with a particular release. I definitely want to hear ideas though!<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks for asking -<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Anne<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<blockquote style="border-style:none none none solid;border-left-color:rgb(204,204,204);border-left-width:1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">thanks in advance,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Greg.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"> </span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12pt"><br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><u></u><u></u></p>
</blockquote>
</div></div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</blockquote></div><br></div></div>