That blueprint doesn't have anything to do with the linked code review, so I'm not sure which you're asking about relative to other projects.
The goal for "Consolidate CLI Authentication" is to allow python-keystoneclient to own the UX around authentication parameters, and allow other clients (e.g. python-openstackclient) to benefit from that work. The v3 auth patch exposed Identity API v3 auth features through the python API, not python-keystoneclient's CLI. Other projects (with the exception of horizon) will eventually benefit for free by consuming keystoneclient.middleware.auth_token. On Fri, Jun 21, 2013 at 7:59 AM, Ciocari, Juliano (Brazil R&D-ECL) < juliano.cioc...@hp.com> wrote: > Hi, > > I have some questions regarding the "Consolidate CLI Authentication" ( > https://etherpad.openstack.org/keystoneclient-cli-auth and > https://review.openstack.org/#/c/21942/). > > It looks like that the code for keystone client is almost ready for merge. > What are the plans for the other clients (nova, glance, etc) to use this > code (if any)? Is there any related change expected on horizon? > > Thanks, > - Juliano > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- -Dolph
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
