OpenStack Service Function Chaining API (Neutron API Extension)
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:/
Blueprint information
- Status:
- Complete
- Approver:
- cathy Hong Zhang
- Priority:
- Undefined
- Drafter:
- cathy Hong Zhang
- Direction:
- Needs approval
- Assignee:
- cathy Hong Zhang
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Louis Fourie
- Completed by
- Louis Fourie
Related branches
Related bugs
Sprints
Whiteboard
This Blueprint is a part of a larger effort: https:/
This Blueprint is moved to networking-sfc from the original Blueprint in Neutron https:/
Gerrit topic: https:/
Neutron API for Service Chaining
Addressed by: https:/
Addressed by: https:/
