Open Stack

..sorry, picking up on this thread again - so it's great that we pull in the keystone client code from these clients - however, we still need to change each of these to pull in the v3 client python code and supply the right parameters (e.g. domain_name) as well as to ask the user for them via the cli so that it can use the keystone code to authenticate.  

Do we not need a co-ordinated effort to ensure all clients can use the v3 code by date X...at which point we know that keystone v3 is fully supported across our clients?

Henry
On 17 May 2013, at 05:01, Chmouel Boudjnah wrote:

> On Thu, May 16, 2013 at 10:40 PM, heckj <heckj at mac.com> wrote:
>> 100% agree with Dolph. Glance already does - and I'm sure there's a few
>> mismatches that have diverged, but having all the clients use auth from a
>> single code location instead of implementing their own and variations will
>> greatly reduce future errors as well.
> 
> +1 as well, FWIW we already do that as well for swiftclient,
> 
> (talking about this I would love to be able delegate command line
> switches as well to keystoneclient).
> 
> Chmouel.
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>