On Mon, Apr 4, 2016 at 7:36 PM, Armando M. <armamig at gmail.com> wrote: > > > On 4 April 2016 at 17:08, Jay Pipes <jaypipes at gmail.com> wrote: >> >> On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote: >>> >>> - why do we even need to control those features with configuration >>> options? can we deprecate and remove them? >> >> >> This would be my choice. Configuration options that make the Neutron API >> behave differently from one deployment to another should be put out to >> pasture. > > > So long as we figure out a way to provide support these capabilities > natively, I agree that we should stop using config options to alter API > behavior. This is undiscoverable by the end user, who is left with the only > choice of poking at the API to see how it responds. > Which is at best an awful user experience. So +1 to removing them. Kyle > Cheers, > Armando > >> >> >> Best, >> -jay >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >