Comment 5 for bug 1450625

On Tue, Oct 6, 2015 at 9:21 PM, Armando Migliaccio <
<email address hidden>> wrote:

> ** Also affects: networking-sfc
> Importance: Undecided
> Status: New
>
> ** No longer affects: neutron
>
> --
> You received this bug notification because you are a member of
> networking-sfc-bugs, which is subscribed to networking-sfc.
> https://bugs.launchpad.net/bugs/1450625
>
> Title:
> common service chaining driver API
>
> Status in networking-sfc:
> New
>
> Bug description:
> This feature/bug is related to bug #1450617 (Neutron extension to
> support service chaining)
>
> Bug #1450617 is to add a neutron port chaining API and associated
> "neutron port chain manager" to support service chaining functionality.
> Between the "neutron port manager" and the underlying service chain
> drivers, a common service chain driver API shim layer is needed to allow
> for different types of service chain drivers (eg. OVS driver, different
> SDN Controller drivers) to be integrated into the Neutron. Different
> service chain drivers may have different ways of constructing the service
> chain path and use different data path encapsulation and transport to steer
> the flow through the chain path. With one common interface between the
> Neutron service chain manager and various vendor-specific drivers, the
> driver design/implementation can be changed without changing the Neutron
> Service Chain Manager and the interface APIs.
>
> This interface should include the following entities:
>
> * An ordered list of service function instance clusters. Each service
> instance cluster represents a group of like service function instances
> which can be used for load distribution.
> * Traffic flow classification rules: It consists of a set of flow
> descriptors.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/networking-sfc/+bug/1450625/+subscriptions
>