On Mon, Feb 10, 2014 at 5:23 PM, Frittoli, Andrea (Cloud Services) < [email protected]> wrote:
> Hi, > > > > Iām working on a tempest blueprint to make tempest able to run 100% on > keystone v3 (or later versions) ā the auth version to be used will be > available via a configuration switch. > > > The rationale is that Keystone V2 is deprecated in icehouse, V3 being the > primary version. Thus it would be good to have (at least) one of the gate > jobs running entirely with keystone v3. > Much appreciated! Have a link to that bp? > > > There are other components beyond tempest that would need some changes to > make this happen. > > > > Nova and cinder python bindings work only with keystone v2 [0], and as far > as I know all core services work with keystone v2 (at least by default). > > Is there a plan to support identity v3 there until the end of icehouse? > Yes (but maybe not by the end of icehouse)- we'd like to make all other client libraries depend on keystoneclient's library for authentication in the long run. Jamie Lennox has done a ton of great work to prepare keystoneclient for that responsibility during Icehouse. > If not I think we may have to consider still supporting v2 in icehouse. > v2 should certainly be supported in icehouse; which version other projects default to is up to them, but I'd like to see *all* projects at least defaulting to v3 by the end of Juno. > > > Andrea > > > > [0] https://bugs.launchpad.net/python-novaclient/+bug/1262843 > > > > -- > > Andrea Frittoli > > IaaS Systems Engineering Team > > HP Cloud ā > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
