Open Stack

On Aug 30, 2012, at 1:51 PM, Chmouel Boudjnah <chmouel at chmouel.com> wrote:

> On Wed, Aug 29, 2012 at 4:06 PM, Chmouel Boudjnah <chmouel at chmouel.com> wrote:
>> I was wondering if somebody attempted to have python-novaclient using
>> python-keystoneclient instead of doing the v2.0 auth.
> 
> As a test I have started doing so for cinder since those two are
> pretty similar :
> 
> https://github.com/chmouel/python-cinderclient/tree/keystoneclient
> 
> there is some stuff available in novaclient/cinderclient not
> implemented in keystoneclient like the proxy_{token/auth_url} and the
> volume/service_name matching.
> 
> The current branch works fine and auth properly (although I need to
> rework the unittests) but I was wondering if those aforementioned
> values in {nova/cinder}client are used and if they are needed in
> keystoneclient.

Yes they are used. the name matching for sure and i think the proxy stuff too.

Vish