[Openstack] Keystone v3 adoption
Aguiar, Glaucimar (Brazil R&D-ECL)
glaucimar.aguiar at hp.com
Thu Mar 7 17:59:17 UTC 2013
Perfect, thanks!
From: Dolph Mathews [mailto:dolph.mathews at gmail.com]
Sent: quinta-feira, 7 de março de 2013 14:56
To: Aguiar, Glaucimar (Brazil R&D-ECL); openstack
Subject: Re: [Openstack] Keystone v3 adoption
Yes, exactly. Until keystoneclient.middleware.auth_token is revised, v3 tokens will basically only be useful against keystone.
-Dolph
On Thu, Mar 7, 2013 at 11:52 AM, Aguiar, Glaucimar (Brazil R&D-ECL) <glaucimar.aguiar at hp.com<mailto:glaucimar.aguiar at hp.com>> wrote:
Hi Dolph,
Thank you very much for your answer. I really appreciate it.
Are you saying then, that I configure nova (for example) to use v3 middleware, I should be able to call nova with a v3 token and this token will get validated?
Glaucimar Aguiar
From: Dolph Mathews [mailto:dolph.mathews at gmail.com<mailto:dolph.mathews at gmail.com>]
Sent: quinta-feira, 7 de março de 2013 11:04
To: Aguiar, Glaucimar (Brazil R&D-ECL)
Cc: openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Subject: Re: [Openstack] Keystone v3 adoption
The v3 API is largely abstracted from other services (horizon being a major exception) using keystoneclient.middleware.auth_token, which is being revised here [1] and here [2].
Because the clients do not necessarily follow the same release schedule as the services, we've obviously been focused on the API and it's server-side implementation. I expect we'll do a v3-compliant release of keystoneclient around the time of grizzly's release. openstackclient (providing CLI exposure) is in the works as well [3].
[1]: https://review.openstack.org/#/c/23401/
[2]: https://review.openstack.org/#/c/21942/
[3]: https://review.openstack.org/#/q/project:openstack/python-openstackclient+status:open,n,z
-Dolph
On Thu, Mar 7, 2013 at 5:30 AM, Aguiar, Glaucimar (Brazil R&D-ECL) <glaucimar.aguiar at hp.com<mailto:glaucimar.aguiar at hp.com>> wrote:
Hello,
I would like to know the plans for nova, glance, etc to adopt keystone v3 API. Is there an expectation that this happens in Havana timeframe?
I am asking as the it seems the Domains feature is not useful until services are capable of validating a v3 token and move to keystone v3 API.
Thanks in advance,
Glaucimar Aguiar
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130307/a224a1c3/attachment.html>
More information about the Openstack
mailing list