Open Stack

On 09/10/2012 02:28 PM, Joseph Heck wrote:
> Hey Boden,
>
> It's not scheduled to be fixed in the Folsom release, the linkages to milestones and such indicate that.
>
> The original developer that proposed a patch disappeared in that flow, so it stagnated. Adam just picked it up and assigned it to himself though to dig around on it - so perhaps he can provide more detail there.

In retrospect, the patch is trivial, and it seems to fit a need.  We 
should be able to sneak it in.  I'm trying to test the CLI right now, 
but the unit tests look good.


>
> -joe
>
>
> On Sep 10, 2012, at 10:31 AM, boden <boden at linux.vnet.ibm.com> wrote:
>> Thanks... Is this defect going to get resolved in the folsom time-frame?
>> Looks like the target milestone was set to none and the defect has been
>> inactive for 2.5 months.
>>
>> On 9/10/2012 12:43 PM, Dolph Mathews wrote:
>>> You thought correct: https://bugs.launchpad.net/keystone/+bug/983304
>>>
>>> -Dolph
>>>
>>>
>>> On Mon, Sep 10, 2012 at 11:32 AM, Adam Young <ayoung at redhat.com
>>> <mailto:ayoung at redhat.com>> wrote:
>>>
>>>     On 09/10/2012 11:29 AM, boden wrote:
>>>
>>>         I've been munking with the latest Keystone LDAP identity driver and
>>>         based on what I'm seeing the driver does not support the 'list'
>>>         resource
>>>         based methods. For example 'list users', 'list tenants'...
>>>
>>>         For example, config your keystone.conf up to use an LDAP backend
>>>         which
>>>         contains the supported DIT structure for the driver and then fire up
>>>         keystone. Hit keystone with a GET /users or GET /tenants request and
>>>         500/501 errors. Switch your identity driver back to the SQL identity
>>>         driver and retry -- all is well and you can list users and tenants.
>>>
>>>         Looking at the code it appears the ldap identity driver does not
>>>         implement the list_*() methods (list_users(), list_roles()...)
>>>
>>>
>>>         _________________________________________________
>>>         Mailing list: https://launchpad.net/~__openstack
>>>         <https://launchpad.net/~openstack>
>>>         Post to     : openstack at lists.launchpad.net
>>>         <mailto:openstack at lists.launchpad.net>
>>>         Unsubscribe : https://launchpad.net/~__openstack
>>>         <https://launchpad.net/~openstack>
>>>         More help   : https://help.launchpad.net/__ListHelp
>>>         <https://help.launchpad.net/ListHelp>
>>>
>>>     That is correct.  I thought we already had a ticket for this one,
>>>     but it does not appear to be so.  Please go ahead and open one.
>>>
>>>     _________________________________________________
>>>     Mailing list: https://launchpad.net/~__openstack
>>>     <https://launchpad.net/~openstack>
>>>     Post to     : openstack at lists.launchpad.net
>>>     <mailto:openstack at lists.launchpad.net>
>>>     Unsubscribe : https://launchpad.net/~__openstack
>>>     <https://launchpad.net/~openstack>
>>>     More help   : https://help.launchpad.net/__ListHelp
>>>     <https://help.launchpad.net/ListHelp>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp