<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace;font-size:small;color:#000000">One more question, what about python-kesytoneclient not being able to fully support v3 api ? for example "keystone tenant-list" (which are called projects) doesnt work.</div>
<div class="gmail_extra"><br clear="all"><div><div><font><b><div class="gmail_default" style="font-family:'courier new',monospace;font-size:small;color:rgb(0,0,0);display:inline">---</div></b></font></div></div><div>
<font><b><div class="gmail_default" style="font-family:'courier new',monospace;font-size:small;color:rgb(0,0,0);display:inline">thx</div></b></font></div><div><font><b><div class="gmail_default" style="font-family:'courier new',monospace;font-size:small;color:rgb(0,0,0);display:inline">
Ale</div></b></font></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">
On Tue, Oct 8, 2013 at 2:21 PM, Adam Young <span dir="ltr"><<a href="mailto:ayoung@redhat.com" target="_blank">ayoung@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div><div>
<div>On 10/07/2013 06:28 PM, Alejandro
Comisario wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>Hi guys, we
have just one question.</div>
<div>
Since we are already traveling our way into deploying havana
release for early 2014, we were stuck under the deep
questioning of the identity api v3.X.</div>
<div>
<br>
</div>
<div>Since we
are using the access to keystone v2.0 identity api a lot,
even from lots of in-house developments, we were thinking
about pushing the use of v3 taking into account that v2
might be discontinued in the near future.</div>
<div>We can do
that from our in-house applications, but wanted to make sure
that v3 API WILL BE supported from all the HAVANA openstack
api endpoints (nova, glance, neutron, cinder, etc) and their
respective python-clients just to justify our internal
change.</div>
</div>
</div>
</blockquote>
<br></div></div>
It is there. Period.<br>
<br>
To test, just point a browser or CURL at <a href="http://hostname:5000/" target="_blank">http://hostname:5000/</a> one
level above the Auth URL, and you will see a list of the supported
versions. 2.0 and v3 are both there. A deployer would have to work
hard to unsupport the V3 API, and I would argue that they were
making a mistake.<br>
<br>
Please do all future development against V3. It is the long lived
apporach, and you work will be better supported. There are several
features, such as domains, that are V3 only.<br>
<br>
<blockquote type="cite"><div>
<div dir="ltr">
<div>
<div><br>
</div>
<div>
Any words about that ?</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>----</div>
<div>
thx</div>
<div>Ale</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div><pre>_______________________________________________
OpenStack-operators mailing list
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br></div></div>