Open Stack

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.

We already provide a way for plugins to claim native support for those  
features, and if they don’t claim it, we fall back to generic  
implementation in Python. Isn’t it enough?

Ihar