Well, I'm certainly not planning on writing a client from scratch, so I'd be happy to hear some discussion on which client we should deem official and replace the others with.
My only concern is that we provide an intuitive python API supporting the various auth flows. -Dolph On Fri, Dec 16, 2011 at 8:43 AM, Julien Danjou <julien.dan...@enovance.com>wrote: > On Fri, Dec 16 2011, Dolph Mathews wrote: > > > Yes (and there's actually more than 2 floating around, in various > states); > > we're moving towards providing a single client, independent of keystone, > > which can be consumed by other projects (including keystone itself). > > > > There's no milestone target for this effort yet, but: > > https://blueprints.launchpad.net/keystone/+spec/keystone-client > > Thanks Dolph, I missed that blueprint. > > Now I think it would be cool if a decision could be done about the > library Gabriel wrote. > > Since it's used by horizon, it seems obvious that it should be > integrated as an official OpenStack component, but, eh… anyone's call? > :) > > -- > Julien Danjou > // eNovance http://enovance.com > // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
