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 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 to > > Keystone that I can think of. > > > > > It was actually broken until John fixed it in: > https://review.openstack.org/#/c/125022/ > > We plan on using it in the Neutron in-tree full-stack testing. I'd appreciate > if the functionality was not removed or otherwise broken :) > > > > > 1. > > https://github.com/openstack/python-neutronclient/commit/2203b013fb66808ef280eff0285318ce21d9bc67#diff-ba2e4fad85e66d9aabb6193f222fcc4cR438 > > > > -- > > Kevin Benton > > > > _______________________________________________ > > OpenStack-dev mailing list > > OpenStack-dev at lists.openstack.org (mailto:OpenStack-dev at lists.openstack.org) > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org (mailto:OpenStack-dev at lists.openstack.org) > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150107/9e590fe3/attachment.html>