On Wed, Feb 18, 2015 at 8:54 PM, Dean Troyer dtro...@gmail.com 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
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)
What I was hoping here was that we could get something in the Neutron
client that works with the
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
On Wed, Feb 18, 2015 at 1:29 PM, Kevin Benton blak...@gmail.com 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
Asking on the operators mailing list may yield more examples where people are
using the Neutron client.
From the CERN perspective, we use OSC heavily now it has Kerberos and X.509
support. With the new support of Keystone V3 in the Nova python client, we are
interested in extending this
