[openstack-dev] [Fuel][Puppet] Keystone V2/V3 service endpoints

Jesse Pretorius jesse.pretorius at gmail.com
Fri Jul 31 12:54:56 UTC 2015

With regards to converting all services to use Keystone v3 endpoints, note
the following:

1) swift-dispersion currently does not support consuming Keystone v3
endpoints [1]. There is a patch merged to master [2] to fix that, but a
backport to kilo is yet to be done.
2) Each type (internal, admin, public) of endpoint created with the
Keystone v3 API has its own unique id, unlike with the v2 API where they're
all created with a single ID. This results in the keystone client being
unable to read the catalog created via the v3 API when querying via the v2
API. The solution is to use the openstack client and to use the v3 API but
this obviously needs to be noted for upgrade impact and operators.
3) When glance is setup to use swift as a back-end, glance_store is unable
to authenticate to swift when the endpoint it uses is a v3 endpoint. There
is a review to master in progress [3] to fix this which is unlikely to make
it into kilo.

We (the openstack-ansible/os-ansible-deployment project) are tracking these
issues and doing tests to figure out all the bits. These are the bugs we've
hit so far. Also note that there is a WIP patch to gate purely on Keystone
v3 API's which is planned to become voting (hopefully) by the end of this

[1] https://bugs.launchpad.net/swift/+bug/1468374
[2] https://review.openstack.org/195131
[3] https://review.openstack.org/193422
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150731/697c7545/attachment.html>

More information about the OpenStack-dev mailing list