[openstack-dev] [cross-project][infra][keystone] Moving towards a Identity v3-only on Devstack - Next Steps
raildom at gmail.com
Thu May 12 15:08:55 UTC 2016
Although the Identity v2 API is deprecated as of Mitaka , some services
haven't implemented proper support to v3 yet. For instance, we implemented
a patch that made DevStack v3 by default that, when merged, broke a lot of
project gates in a few hours . This happened due to specific services in
compatibility issues with Keystone v3 API, such as hardcoded v2 usage,
usage of removed keystoneclient CLI, requesting v2 service tokens and the
lack of keystoneauth session usage.
To discuss those points, we did a cross-project work session in the Newton
Summit. One point we are working on at this momment is creating gates to
ensure the main OpenStack services can live without the Keystone v2 API. Those
gates setup devstack with only Identity v3 enabled and run the Tempest suite
on this environment.
We already did that for a few services, like Nova, Cinder, Glance, Neutron,
Swift. We are doing the same job for other services such as Ironic, Magnum,
Ceilometer, Heat and Barbican .
In addition, we are creating jobs to run functional tests for the services
on this identity v3-only environment. Also, we have a couple of other
fronts that we are doing like removing some hardcoded v2 usage ,
implementing keystoneauth sessions support in clients and APIs .
Our plan is to keep tackling as many items from the cross-project session
etherpad as we can, so we can achieve more confidence in moving to a DevStack
working v3-only, making sure everyone is prepared to work with Keystone v3
Feedbacks and reviews are very appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev