On Wed, Feb 18, 2015 at 8:54 PM, Dean Troyer wrote:
> I think one thing needs to be clarified...what you are talking about is
> utilizing keystoneclient's auth plugins in neutronclient. Phrasing it as
> 'novaclient parity' reinforces the old notion that novaclient is the model
> for doing things
On Wed, Feb 18, 2015 at 1:29 PM, Kevin Benton wrote:
> Perhaps I am misunderstanding, but doesn't the OSC support for pluggable
> auth just come for free from Neutron's perspective? (i.e. we don't have to
> make any Neutron-specific changes for that to work)
>
It does if/when the command layer w
>
>
>
> *From:* Kevin Benton [mailto:blak...@gmail.com]
> *Sent:* 18 February 2015 20:01
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] Pluggable Auth for clients and where
> should it go
>
>
>
> This is something
2015 20:01
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Pluggable Auth for clients and where should it go
This is something I have been working on internally as well. I've been trying
to find a way to make the changes to the python neutronclie
This is something I have been working on internally as well. I've been
trying to find a way to make the changes to the python neutronclient in the
least invasive way to support pluggable authentication. I would be happy to
help review the changes you submit upstream if you have something already
we
Just starting this discussion…
This is in reference to
https://blueprints.launchpad.net/python-neutronclient/+spec/pluggable-neutronclient-auth
Originally the blueprint was for python-neutronclient only, but pluggable auth
is a wide-reaching issue. With OSC/SDK on the horizon (however far), we
