Open Stack

On Mon, Apr 22, 2013 at 7:52 PM, Dolph Mathews <dolph.mathews at gmail.com> wrote:
>> Why can't the ec2 token middleware live in Nova?
> or novaclient or keystoneclient, given the precedence of
> keystoneclient.middleware.auth_token?

I'd love to move ec2/s3-token to keystoneclient as this is better
suited there if there is no objections i will send a patch (with a
compat stub in keystone like it done in auth_token).

>>   1) Fix it so that importing the ec2 middleware doesn't import all of
>>      keystone's config options via the import in keystone.middleware
> I couldn't find a way to do this when working on
> https://bugs.launchpad.net/nova/+bug/1143998
> I ended up implementing a workaround which might work for ec2_token as well?
> See:
>   https://review.openstack.org/#/c/24701/

nice, I may just do that after the move to the ksclient.

Chmouel.