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 -Dolph On Fri, Dec 16, 2011 at 8:05 AM, Julien Danjou <[email protected]>wrote: > Hi, > > I've just a small question about Keystone client code. > > Correct me if I'm wrong, but it seems that currently there's Keystone > client code inside python-novaclient as novaclient.keystone. OTOH, > horizon seems to use python-keystoneclient which is not part of > OpenStack. > > I don't see the point to have 2 clients libraries and use them both in > the project. Is there a goal to unify these two, to drop one, or > anything? > > -- > Julien Danjou > // eNovance http://enovance.com > // ✉ [email protected] ☎ +33 1 49 70 99 81 > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
