Service Function Chaining is a mechanism for overriding the basic destination based forwarding that is typical of IP networks. It is conceptually related to Policy Based Routing in physical networks but it is typically thought of as a Software Defined Networking technology. It is often used in conjunction with security functions although it may be used for a broader range of features. Fundamentally SFC is the ability to cause network packet flows to route through a network via a path other than the one that would be chosen by routing table lookups on the packet’s destination IP address. It is most commonly used in conjunction with Network Function Virtualization when recreating in a virtual environment a series of network functions that would have traditionally been implemented as a collection of physical network devices connected in series by cables.
A very simple example of a service chain would be one that forces all traffic from point A to point B to go through a firewall even though the firewall is not literally between point A and B from a routing table perspective. A more complex example is an ordered series of functions, each implemented in multiple VMs, such that traffic must flow through one VM at each hop in the chain but the network uses a hashing algorithm to distribute different flows across multiple VMs at each hop.
Cathy Zhang (Project Lead)
Ramanjaneya Reddy Palleti
Igor Duarte Cardoso
All code Code
- Version control system:
- Programming languages:
All questions Latest questions
stack.sh fails during networking-sfc plugin installation
Posted on 2016-11-08
traffic redirection not working
Posted on 2016-10-13
DevStack: stack.sh stuck at neutron-ovs-cleanup for a long time
Posted on 2016-10-04
The type of service function
Posted on 2016-07-19
Does networking-sfc ovs-agent support source/destination vm and service funct...
Posted on 2016-01-23
All bugs Latest bugs reported
Bug #1667485: Tempest gate broken after switch to local.conf in devstack-gate
Reported 6 hours ago
Bug #1666568: OVS driver unit tests random failure: "AssertionError: Mismatched values: 'source_ip_prefix', expected: u'10.0.0.9', actual: u'10.0.0.10'"
Reported on 2017-02-21
Bug #1665960: logical-source-port with IP prefix may create incorrect chains
Reported on 2017-02-19
Bug #1665406: OVS DB issues
Reported on 2017-02-16
Bug #1663877: PEP8 checks are being ignored
Reported on 2017-02-11