This session will include the following subject(s):
Flavor framework for advanced services:
This session should cover requirements and design of 'Flavor Framework' - a new API proposal that should allow users to specify service requirements based on capabilities rather than directly choose provider/vendor
(Session proposed by Eugene Nikanorov)
Virtual Resource for Service Chaining:
Discuss an alternative way of service chaining implementation. A chain of services can be represented by introduction of the notion of virtual network resource.
(Session proposed by IWAMOTO Toshihiro)
Neutron "Advanced Services" Common Requirements:
Besides basic L2 connectivity, all other aspects of network connectivity are considered as "advanced services" in Neutron. This includes L3/routing and L4-7 (like FWaaS, LBaaS, VPNaaS) features. While each individual advanced service is fairly well defined, there aren't enough normalizing constructs for users to select among different types of the same service (the services may differ in their capabilities), and/or to express the deployment of a combination of services (as a service chain). In addition, a common backend framework does not exist to handle service insertion and chaining. A few proposals have already been made in this context (e.g. service flavors, service context). In this session we will try to build consensus among the different sub-teams on these proposals and the roadmap for Juno.
