Me, not being aware that we were already moving towards supporting python-keystoneclient, implied that someone was /against/ python-keystoneclient.
I have no objections :) -Dolph Mathews On Dec 16, 2011, at 4:56 PM, Ziad Sawalha <[email protected]> wrote: > Who suggested not using python-keystoneclient? > > > > On 12/16/11 4:12 PM, "Jesse Andrews" <[email protected]> wrote: > >> python-keystoneclient is based on python-novaclient, and is already in >> use by horizon as mentioned. >> >> What are the reasons for not using python-keystoneclient? >> >> Jesse >> >> On Fri, Dec 16, 2011 at 1:47 PM, Monty Taylor <[email protected]> >> wrote: >>> Hrm. For some reason I thought we'd already decided to use the >>> 4P/python-keystoneclient (it's been a todo list item for me to move it >>> in to the openstack repos) I take it that we have _not_ decided that we >>> should use that library as the keystone client library? >>> >>> >>> >>> On 12/16/2011 10:16 AM, Dolph Mathews wrote: >>>> 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 >>>> <[email protected] <mailto:[email protected]>> 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 >>>> // ✉ [email protected] <mailto:[email protected]> >>>> ☎ +33 1 49 70 99 81 <tel:%2B33%201%2049%2070%2099%2081> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> 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 _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
