<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 8, 2013 at 4:54 PM, Gabriel Hurley <span dir="ltr"><<a href="mailto:Gabriel.Hurley@nebula.com" target="_blank">Gabriel.Hurley@nebula.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=""><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Identity service has both a v2.0 and v3 side-by-side. There isn’t necessarily a “default” except for the fact that most people’s Service Catalogs still say
“v2.0” in them because they’re hard-coded that way.<u></u><u></u></span></p>
<p class=""><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 style>Wow, really? I have asked and asked about that API in particular and still don't understand how that really works. Can you explain more about how that can happen other than mis-labeled endpoints?</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=""><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u></span></p>
<p class=""><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">In the future I believe the <a href="http://api.openstack.org" target="_blank">api.openstack.org</a> site would gain a lot by storing documentation for each version of the API for historical purposes, legacy deployments,
etc. Sure would help me, too. ;-)</span></p></div></div></blockquote><div style><br></div>Could you explain more about what "storing documentation for each version of the API for historical purposes" would look like to you? We have all versions (v 1.1, v2, v3.0) of each API spec stored. Do you want them published as well? We do so for Image API for example. Tell me more. <div style>
Anne</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=""><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class=""><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p style="margin-left:27pt">
<u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><span>-<span style="font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Gabriel<u></u><u></u></span></p>
<p class=""><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<div style="border-style:none none none solid;border-left-color:blue;border-left-width:1.5pt;padding:0in 0in 0in 4pt">
<div>
<div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in">
<p class=""><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"> Openstack [mailto:<a href="mailto:openstack-bounces%2Bgabriel.hurley" target="_blank">openstack-bounces+gabriel.hurley</a>=<a href="mailto:nebula.com@lists.launchpad.net" target="_blank">nebula.com@lists.launchpad.net</a>]
<b>On Behalf Of </b>Anne Gentle<br>
<b>Sent:</b> Wednesday, May 08, 2013 2:44 PM<br>
<b>To:</b> Devendra Gupta<br>
<b>Cc:</b> <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
<b>Subject:</b> Re: [Openstack] API version in Grizzly<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class=""><u></u> <u></u></p>
<div>
<p class="">Hi Devendra,<u></u><u></u></p>
<div>
<p class="">Generally the guidance for the <a href="http://api.openstack.org" target="_blank">
api.openstack.org</a> site is to publish documents that reflect the latest version, grizzly, as the underlying implementation for the API. However the cloud provider can pick and choose which extensions they have in place, for example, so some Compute extensions
may be unavailable on essex for example. <u></u><u></u></p>
</div>
<div>
<p class=""><u></u> <u></u></p>
</div>
<div>
<p class="">Generally I believe this list of API versions is true for Grizzly default implementations. PTLs please correct as needed:<br>
<br>
Identity Service API 2.0<u></u><u></u></p>
</div>
<div>
<p class="">Compute API 2 and Extensions<br>
Image Service API 2 (a provider could choose to implement v1)<br>
Object Storage API 1.0<br>
Networking API 2.0<br>
Block Storage Service API 2.0<u></u><u></u></p>
</div>
<div>
<p class=""><u></u> <u></u></p>
</div>
<div>
<p class="">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="">Anne<u></u><u></u></p>
</div>
</div>
<div>
<p class="" style="margin-bottom:12pt"><u></u> <u></u></p>
<div>
<p class="">On Wed, May 8, 2013 at 3:23 PM, Devendra Gupta <<a href="mailto:dev29aug@gmail.com" target="_blank">dev29aug@gmail.com</a>> wrote:<u></u><u></u></p>
<p class="">Hi,<br>
<br>
I am trying to find the lasted stable API versions of all the OpenStack<br>
components, I am looking around in OpenStack docs but unable to see some<br>
specific page which says about particular version of APIs are available<br>
with Grizzly.<br>
<br>
I can see following pages but they don't say what version of API is<br>
latest stable with Grizzly.<br>
<br>
<a href="http://docs.openstack.org/api/api-specs.html" target="_blank">http://docs.openstack.org/api/api-specs.html</a><br>
<a href="http://api.openstack.org/api-ref.html" target="_blank">http://api.openstack.org/api-ref.html</a><br>
<br>
I need this information to plan some work related to OpenStack, guidance<br>
around this would be highly appreciate.<br>
<br>
Thanks,<br>
Devendra<br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><u></u><u></u></p>
</div>
<p class=""><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</div>
</blockquote></div><br></div></div>