<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div><font color="#1F497D">In Grizzly I can send Keystone requests to either <a href="http://<keystone_host>:5000/v2.0/"><font color="blue"><u>http://<keyston</u></font><font color="blue"><u>e_host>:5000/v2.0/</u></font></a> or to <a href="http://<keystone_host>:5000/v3/"><font color="blue"><u>http://<keystone_host>:5000/v3/</u></font></a>
and both work just fine (provided I send the right request). Both APIs are enabled, and simply have different API controllers wired to different code paths under the hood. The only thing making one “default” is the fact that DevStack (and by extension a lot
of guides and a lot of people’s existing copy-pasted installations) have the Keystone v2.0 endpoint hard-coded into the service catalog. See the various threads and my TC proposal for further detail on what I think about that fact and what to do with it going
forward.</font></div>
<div><font face="Times New Roman" size="3" color="#1F497D"><span style="font-size:12pt;"> </span></font></div>
<div><font color="#1F497D">As for api.openstack.org, I always look at the “Complete Reference” (<a href="http://api.openstack.org/api-ref.html"><font color="blue"><u>http://api.openstack.org/api-ref.html</u></font></a>) which lists one version for each service
API (currently still Keystone v2.0). As long as you’re taking feature requests, what I’d *<b>like</b>* to see when I land on that page is a collapsed list of each service API type (e.g. Identity, Compute, etc.) which I can then expand, revealing the list of
available versions. Expanding one of those should yield what I currently see on the Complete Reference page. <font face="Wingdings">J</font></font></div>
<div><font face="Times New Roman" size="3" color="#1F497D"><span style="font-size:12pt;"> </span></font></div>
<div><font color="#1F497D">All the best,</font></div>
<div><font color="#1F497D"> </font></div>
<ul style="margin:0;padding-left:27pt;">
<font color="#1F497D">
<li>Gabriel</li></font>
</ul>
<div><font face="Times New Roman" size="3" color="#1F497D"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Tahoma" size="2"><span style="font-size:10pt;"><b>From:</b> annegentle@justwriteclick.com [<a href="mailto:annegentle@justwriteclick.com">mailto:annegentle@justwriteclick.com</a>] <b>On Behalf Of </b>Anne Gentle<br>
<b>Sent:</b> Wednesday, May 08, 2013 4:38 PM<br>
<b>To:</b> Gabriel Hurley<br>
<b>Cc:</b> Devendra Gupta; openstack@lists.launchpad.net<br>
<b>Subject:</b> Re: [Openstack] API version in Grizzly</span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div style="margin-bottom:12pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;">On Wed, May 8, 2013 at 4:54 PM, Gabriel Hurley <<a href="mailto:Gabriel.Hurley@nebula.com"><font color="blue"><u>Gabriel.Hurley@nebula.com</u></font></a>> wrote:</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font color="#1F497D">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.</font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font color="#1F497D"> </font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;">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?</span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font color="#1F497D">In the future I believe the <a href="http://api.openstack.org"><font color="blue"><u>api.openstack.org</u></font></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. ;-)</font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;">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. </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;">Anne</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font color="#1F497D"> </font></div>
<div style="margin-top:5pt;margin-bottom:5pt;padding-left:27pt;"><font color="#1F497D">-<font face="Times New Roman" size="1"><span style="font-size:7pt;"> </span></font>Gabriel</font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font color="#1F497D"> </font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Tahoma" size="2"><span style="font-size:10pt;"><b>From:</b> Openstack [mailto:<a href="mailto:openstack-bounces%2Bgabriel.hurley"><font color="blue"><u>openstack-bounces+gabriel.hurley</u></font></a>=<a href="mailto:nebula.com@lists.launchpad.net"><font color="blue"><u>nebula.com@lists.launchpad.net</u></font></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"><font color="blue"><u>openstack@lists.launchpad.net</u></font></a><br>
<b>Subject:</b> Re: [Openstack] API version in Grizzly</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;">Hi Devendra,</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;">Generally the guidance for the <a href="http://api.openstack.org"><font color="blue"><u>api.openstack.org</u></font></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. </span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;">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</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;">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</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;">Thanks,</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;">Anne</span></font></div>
<div style="margin-top:5pt;margin-bottom:12pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;">On Wed, May 8, 2013 at 3:23 PM, Devendra Gupta <<a href="mailto:dev29aug@gmail.com"><font color="blue"><u>dev29aug@gmail.com</u></font></a>> wrote:</span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;">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"><font color="blue"><u>http://docs.openstack.org/api/api-specs.html</u></font></a><br>
<a href="http://api.openstack.org/api-ref.html"><font color="blue"><u>http://api.openstack.org/api-ref.html</u></font></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"><font color="blue"><u>https://launchpad.net/~openstack</u></font></a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net"><font color="blue"><u>openstack@lists.launchpad.net</u></font></a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack"><font color="blue"><u>https://launchpad.net/~openstack</u></font></a><br>
More help : <a href="https://help.launchpad.net/ListHelp"><font color="blue"><u>https://help.launchpad.net/ListHelp</u></font></a></span></font></div>
<div style="margin-top:5pt;margin-bottom:5pt;"><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"> </span></font></div>
</span></font>
</body>
</html>