Open Stack

German <german.eichberger at hpe.com> wrote:

> Ihar,
>
> The Service Group API will be added to FWaaS only and remain experimental  
> in M. If the community finds it useful for other areas it can be added to  
> Neutron core once it is matures. I think incubating it inside FWaaS will  
> give us the velocity to iterate quickly and once it matures a strong API  
> for adoption in the wider Neutron.
>
> On the other hand if classifiers mature more quickly/provide the same  
> functionality more elegantly we can quickly pivot to that. Since we are  
> trying to address an immediate need I would like to experiment with  
> Service Groups inside FWaaS first and then use that to shape the  
> classifier API discussion. Also, as Sean suggested, we might use the  
> classifier data models under the hood — so despite being a different API  
> at first we might arrive at the same shared implementation…

Thanks for clarification! If we are aware of compatibility issues and use  
API in experimental features only, I think that’s indeed a better approach.  
 From the first sight at the service group spec, I haven’t seen any marks  
of its experimental nature, hence was asking.

Thanks again,
Ihar