Neutron API Extension For Service Chaining

Registered by cathy Hong Zhang on 2015-04-21

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

All Neutron network services and VMs are connected to a Neutron network via Neutron ports. This makes it possible to create a traffic steering model for service chaining that uses only Neutron ports. This traffic steering model has no notion of the actual services attached to these Neutron ports.

The network service function is instantiated and configured, and then it is connected to the network through Neutron ports. Once the service function is attached to Neutron ports, the ports may be included in a "port chain" to allow the service function to provide treatment to the user's traffic.

Please refer to the spec for more details: https://review.openstack.org/#/c/192933/

Blueprint information

Status:
Complete
Approver:
Kyle Mestery
Priority:
Undefined
Drafter:
cathy Hong Zhang
Direction:
Needs approval
Assignee:
cathy Hong Zhang
Definition:
Superseded
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Armando Migliaccio on 2015-11-13

Related branches

Sprints

Whiteboard

Moved to networking-sfc.

This Blueprint is a part of a larger effort: https://blueprints.launchpad.net/neutron/+spec/openstack-service-chain-framework

Gerrit topic: https://review.openstack.org/#/q/topic:networking-sfc,n,z

 Neutron API for Service Chaining
Addressed by: https://review.openstack.org/#/c/204695

Addressed by: https://review.openstack.org/#/c/192933/

(?)

Work Items