yahoo-eng-team team mailing list archive

[cathy Hong Zhang <cathy.h.zhang@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
     Assignee: cathy Hong Zhang (cathy-h-zhang)
         Status: In Progress


** Tags: rfe

** Changed in: neutron
     Assignee: (unassigned) => cathy Hong Zhang (cathy-h-zhang)

** Changed in: neutron
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1450617

Title:
  Neutron extension to support service chaining

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  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