Re: [openstack-dev] [Neutron] Enabling/Disabling specific API extensions

2016-06-07 Thread Kevin Benton
I think we want to be careful about allowing every extension to be configurable by the operator because plugins might expect certain extensions to be loaded since they are defined in code. I suppose we could have a way that it is just disabled at the API level but all of the code is still loaded,

Re: [openstack-dev] [Neutron] Enabling/Disabling specific API extensions

2016-06-07 Thread Brandon Logan
On Tue, 2016-06-07 at 19:17 +, Sean M. Collins wrote: > The patch that switches DevStack over to using the Neutron API to > discover what features are available has landed. > > https://review.openstack.org/#/c/318145/7 > > The quick summary is that things like Q_L3_ENABLED[1] and if certain

[openstack-dev] [Neutron] Enabling/Disabling specific API extensions

2016-06-07 Thread Sean M. Collins
The patch that switches DevStack over to using the Neutron API to discover what features are available has landed. https://review.openstack.org/#/c/318145/7 The quick summary is that things like Q_L3_ENABLED[1] and if certain services are running/enabled has been replaced with checks for if an