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) < [email protected]> 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 : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
