On 3/19/2014 10:02 AM, Matthew Treinish wrote:
On Wed, Mar 19, 2014 at 09:35:34AM -0500, Matt Riedemann wrote:


On 3/19/2014 2:48 AM, Shao Kai SK Li wrote:
Hello:

      I am working on this
patch(https://review.openstack.org/#/c/77524/) to fix bugs about volume
attach failure with keystone V3 token.

      Just wonder, is there some blue prints or plans in Juno to address
keystone V3 support in nova ?

      Thanks you in advance.


Best Regards~~~

Li, Shaokai


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


I have this on the nova meeting agenda for tomorrow [1].  I would
think at a minimum this means running compute tests in Tempest
against a keystone v3 backend.  I'm not sure what the current state
of Tempest is regarding keystone v3.  Note that this isn't the only
thing that made it into nova in Icehouse related to keystone v3 [2].

On the tempest side there are some dedicated keystone v3 api tests, I'm not
sure how well things are covered there though. On using keystone v3 for auth
for the other tests tempest doesn't quite support that yet. Andrea Frittoli is
working on a bp to get this working:

https://blueprints.launchpad.net/tempest/+spec/multi-keystone-api-version-tests

But, at this point it will probably end up being early Juno thing before this
can be enabled everywhere in tempest.

-Matt Treinish

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Furthermore Russell talked to Dolph in IRC and Dolph created this blueprint for planning the path forward from keystone v2 to v3:

https://blueprints.launchpad.net/keystone/+spec/document-v2-to-v3-transition

--

Thanks,

Matt Riedemann


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to