Seems like a good reason to keep it, this allows us to test
internal integration in isolation from keystone.
Miguel Ángel Ajo
On Wednesday, 7 de January de 2015 at 10:05, Assaf Muller wrote:
- Original Message -
The option to disable keystone authentication in the neutron
- Original Message -
The option to disable keystone authentication in the neutron client was
marked for deprecation in August as part of a Keystone support upgrade.[1]
What was the reason for this? As far as I can tell, Neutron works fine in the
'noauth' mode and there isn't a lot
Adding to what Miguel said, I've merged a few months back a patch [1]
which actually fixed the noauth feature in favour of the full-stack
effort (the full-stack patches use neutronclient in noauth mode for easy
access to neutron-server). We'll probably continue to use neutronclient
until some
The option to disable keystone authentication in the neutron client was
marked for deprecation in August as part of a Keystone support upgrade.[1]
What was the reason for this? As far as I can tell, Neutron works fine in
the 'noauth' mode and there isn't a lot of code that tightly couples
neutron
