Comment 10 for bug 1450617

Akihiro,

Yes, the activity is in progress in networking-sfc. We can use this bug as a place holder to include this feature in OpenStack release when the codes are ready and merged. What do you think?

Thanks,
Cathy

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Akihiro Motoki
Sent: Tuesday, October 06, 2015 3:39 AM
To: Cathy Zhang
Subject: [Bug 1450617] Re: Neutron extension to support service chaining

The actual activity is in progress in networking-sfc project.
I wonder what is the best way to handle this RFE bug.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1450617

Title:
  Neutron extension to support service chaining

Status in neutron:
  Triaged

Bug description:
  In current Data Center, the deployment of service chain for a tenant's flow is through static, complex, and rigid configurations since they are tightly coupled with physical network topology and physical resources. The introduction of new services into a network usually requires the reconfiguration of most (if not all)
  network elements. This is not acceptable in cloud environment. To reduce the OPEX and increase agility, automatic setup of service chain according to user's service chain requirement specification is needed. There is already a BP submitted on service chain use case https://review.openstack.org/#/c/169201/4

  Currently Neutron does not support service chaining. To support
  service chaining, Service VMs must be attached to points of the
  network and then traffic must be steered between these attachment
  points.

  There are two steps in creating a service chain. First, Services VMs
  (such as FW VM) need to be created and connected to a Neutron network
  via Neutron ports. After that, selected traffic flows need to be
  steered through an ordered sequence of these service VM ports. Current
  OpenStack already support creation of service VMs and attachment of
  these service VMs to Neutron network ports. What is missing is an API
  to specify classification rules of the selected flow and the sequence
  of service VM ports the selected flow needs to go through so that it
  can get the desired service treatment. Neutron API can be extended to
  fill in this gap. This new "port chain" API does not need to know the
  actual services attached to these Neutron ports since the Service VM
  creation API already has this information.

  In summary, first the service function is instantiated and connected
  to the network through Neutron ports. Once the service function is
  attached to Neutron ports, the ports are included in a "port chain" to
  allow the service function to provide treatment to the user's traffic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1450617/+subscriptions