User Tools

Site Tools


network_function_chaining

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
network_function_chaining [2015/03/25 12:30]
Christopher Price
network_function_chaining [2015/05/06 01:53]
Daniel Farrell [Scope] Fix minor capitalization and formatting errors
Line 1: Line 1:
 ====== OPNFV Service Function Chaining ====== ====== OPNFV Service Function Chaining ======
  
-==== Project Name====+==== Project Name ====
  
   * Proposed name for the project: ''​OPNFV Service Function Chaining''​   * Proposed name for the project: ''​OPNFV Service Function Chaining''​
Line 10: Line 10:
 ===== Project description ===== ===== Project description =====
  
-This project will create a link between two LINUX Foundation projects, ​Opendaylight ​(ODL) and OPNFV. One of the goals is to allow Opendaylight ​to create Service Function Chains across OPNFV Network Functions (NFs).+This project will create a link between two Linux Foundation projects, ​OpenDaylight ​(ODL) and OPNFV. One of the goals is to allow OpenDaylight ​to create Service Function Chains across OPNFV Network Functions (NFs).
 The use-case for chaining Network Functions is discussed in “Network Functions Virtualisation (NFV); Architectural Framework, ETSI GS NFV 002 V1.1.1 (2013-10)”,​ section 6. The use-case for chaining Network Functions is discussed in “Network Functions Virtualisation (NFV); Architectural Framework, ETSI GS NFV 002 V1.1.1 (2013-10)”,​ section 6.
                 ​                 ​
-Opendaylight ​already ​have capability to create Service Function Chains (https://​wiki.opendaylight.org/​view/​Service_Function_Chainingand will be extended as appropriate to specifically control OPNFV NFs. +OpenDaylight ​already ​has the [[https://​wiki.opendaylight.org/​view/​Service_Function_Chaining:Main | capability to create Service Function Chains]] ​and will be extended as appropriate to specifically control OPNFV NFs.
  
 +This collaborative development project will work with the [[https://​wiki.opnfv.org/​requirements_projects/​openstack_based_vnf_forwarding_graph | "​OpenStack Based VNF Forwarding Graph“]] requirement project to achieve the best interoperability and embedding into the NFV environment.
 ===== Scope ===== ===== Scope =====
  
-Service Function Chaining ​ is a key technology identified to help with the deployment and networking of VNFs in NVF environments. ​ The project will work with the upstream communities in OVS, OpenDaylight and OpenStack to develop functionality needed to provide service chaining capabilities in the OPNFV platform.+Service Function Chaining is a key technology identified to help with the deployment and networking of VNFs in NVF environments. The project will work with the upstream communities in OVS, OpenDaylight and OpenStack to develop functionality needed to provide service chaining capabilities in the OPNFV platform.
  
-Service chaining technologies provided by the OpenDaylight SFC implementation and intended to be integrated in the OPNFV platform include:+Service chaining technologies provided by the OpenDaylight SFC implementation and intended to be integrated in the OPNFV platform ​currently ​include:
   * OpenFlow programmed service chains for:   * OpenFlow programmed service chains for:
     * L2 VLAN encapsulation     * L2 VLAN encapsulation
     * MPLS encapsulation     * MPLS encapsulation
-  * VxLan overlay ​base service chains for: +  * VXLAN overlay ​based service chains for: 
-    * VxLan + GPE encapsulation with NSH headers+    * VXLAN-GPE encapsulation with NSH headers
   * Basic load balancing at SFC (planned for ODL Lithium)   * Basic load balancing at SFC (planned for ODL Lithium)
   * Programmatic service function selection algorithms   * Programmatic service function selection algorithms
     * Round robin     * Round robin
-    * Load balanced+    * Load balanced ​(choose the least loaded service function)
     * Random allocation     * Random allocation
-Future development will include hybrid service chains, support for layer 4-7 classification,​ additional encapsulations,​ additional load balancing and service function instance selection algorithms. ​+Future development will include hybrid service chains ​(OVS and/or OFS), support for layer 4-7 classification,​ additional encapsulations,​ additional load balancing and service function instance selection algorithms. ​
  
 ==== Testing ==== ==== Testing ====
Line 39: Line 40:
 The service chaining project will develop test cases in the robot toolchain provided by these projects. The service chaining project will develop test cases in the robot toolchain provided by these projects.
  
-==== Documentation: ''​(optional,​ Project Categories: Documention)'' ​====+==== Documentation ====
  
 +The service chaining project will develop documentation as described by the OPNFV documentation project and associated toolchain. ​ These documents will include:
 +  * Service Chaining user guide
 +  * API Documentation
 +  * Release documentation including test coverage.
  
-  * API Docs +==== Dependencies ====
-  * Functional block description+
  
-==== Dependencies:​ ==== +  ​The OPNFV Service Function Chaining project implements the ODL-related components of the features described in the '//​OpenStack Based VNF Forwarding Graph//' ​project 
- +    Service Function Chaining does not at this time implement the SCH header, nor support multiple SC controllers per OpenStack instance
-  ​Identify similar projects is underway or being proposed in OPNFV or upstream ​project +    The SFC project will coordinate and cooperate ​with the VNFFG project ​on realizing target use cases and consistent encapsulations (MPLSVXLAN overlay, NSH, etc.) 
-  Identify any open source upstream projects and release timeline.  +  * The OPNFV Service Function Chaining ​project is dependant on the following upstream communities
-  Identify any specific development be staged ​with respect to the upstream ​project and releases. +    * OpenStack 
-  * Are there any external fora or standard development organization dependencies. If possiblelist and informative and normative reference specifications+    OpenDaylight 
-  * If project is an integration and test, identify hardware dependency. +    OVS 
- +  * OPNFV SFC is dependant on the Lithium ​release of OpenDaylight and the Kilo release of OpenStack and OVS data plane extensions for Network Function Chaining[[https://​github.com/​priteshk/​ovs.git]] 
-==== Committers and Contributors==== +    The functional scope of SFC in OPNFV release ​2 will be dependant on stable releases of these projects being available. ​   
- +  * SFC is currently implemented in reference to the following standards bodies and activities
-  Names and affiliations of the committers +    EITF Service Function Chaining architecture and NSH headers: [[http://tools.ietf.org/html/draft-quinn-sfc-nsh-07| IETF NSH draft]] 
-  Names and affiliations of any other contributors +    ONF service function chaining architecture and OpenFlow[[https://www.opennetworking.org/images/​stories/​downloads/sdn-resources/solution-briefs/sb-sdn-nvf-solution.pdf|ONF sb-sdn-nvf-solution.pdf]] 
- +    ETSI NFV ISG Use case 4, VNF Forwarding Graphs: ​[[http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf|GS NFV 001 Network Functions Virtualisation]] 
-==== Planned deliverables ==== +==== Committers and Contributors ​==== 
- +Project Leader 
-  * Described ​the project ​release ​package as OPNFV or open source upstream projects. +  * Brady Johnson (brady.allen.johnson@ericsson.com) 
-  * If project deliverables have multiple dependencies across other project categories, described linkage ​of the deliverables. +Committers
- +
-==== Proposed Release Schedule==== +
- +
-  ​When is the first release ​planned? +
-  * Will this align with the current release cadence +
- +
- +
-Use the above information to create a key project facts section on your project page +
-===== Key Project Facts ===== +
- +
-** Project Name** Project Name (repo name) \\ +
-** Repo name** \\ +
-** Project Category: ** \\ +
-** Lifecycle State: ** \\ +
-** Primary Contact: ** \\ +
-** Project Lead: ** \\ +
-** Jira Project Name: ** Same as Project name \\ +
-** Jira Project Prefix: ** [10 Characters max [A-Z] ] \\ +
-** mailing list tag ** [Should match Jira Project Prefix] \\ +
-** Committers: ** \\ +
-foo@bar.com \\ +
-baz@qux.com \\ +
-** Link to TSC approval: Example ​http://meetbot.opnfv.org/meetings/opnfv-meeting/​2015/​opnfv-meeting.2015-03-03-15.01.html ** \\  +
-** Link to approval of additional submitters** Example http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html \\ +
- +
- +
- +
-  ​Service Function Chaining and Group Based Policy Integration in the context of OPNFV. The basic integration spec can be found at [[https://wiki.opendaylight.org/view/Service_Function_Chaining:​Group_Based_Policy_Integration]] +
-  * Investigate a user-space VXLAN-GPE+NSH module for DPDK-netdev +
-  * Hardware Based Acceleration for NSH+VXLAN +
-  * A RESTConf based self-registration methods that allows OPNFV NFs to announce their Service Chaining capabilities to ODL +
-  * An OPNFV RESTconf interface based on the SFC Yang models https://github.com/opendaylight/sfc/​tree/​master/​sfc-model/​src/​main/​yang that will allow ODL to create Service Chains using OPNFV NFs +
-  * Investigate how NSH network function chaining can be used in Openstack networks, what changes would be needed and how to best implement them +
-  * Interoperability testing between ODL and OPNFV NFs +
- +
- +
-  * OVS data plane extensions for Network Function ChainingThe current NSH  [[http://tools.ietf.org/​html/​draft-quinn-sfc-nsh-07]]  OVS patch can be found in: +
- +
-      git clone https://​github.com/​priteshk/​ovs.git +
-      git checkout nsh-v8 +
- +
- +
- +
-===== Documentation ===== +
- +
-  * Functional Architecture Specification +
-  * Release Notes +
-  * Sample Application User Guide +
- +
-===== Committers ​and Contributors ===== +
-    ​+
   * Reinaldo Penno (rapenno@gmail.com)   * Reinaldo Penno (rapenno@gmail.com)
   * Paul Quinn (paulq@cisco.com)   * Paul Quinn (paulq@cisco.com)
Line 120: Line 73:
   * Vishal Murgai (vmurgai@gmail.com)   * Vishal Murgai (vmurgai@gmail.com)
   * Kiran Sreenivasa(kkoushik@brocade.com)   * Kiran Sreenivasa(kkoushik@brocade.com)
-  ​Brady Johnson ​(brady.allen.johnson@ericsson.com)+Contributors 
 +  ​Christopher Price (christopher.price@ericsson.com)
  
-===== Testing ===== +==== Planned ​deliverables ​====
- +
-  * Implementation of a regression testing suite +
-  * Interoperability testing between ODL and OPNFV NF +
-  * Interoperability testing between SFC ODL and Openstack  +
-  * Implementation of system test suite across ODL and OPNFV NFs +
- +
-===== Planned ​Deliverable =====+
  
 +  * OPNFV Service Function Chaining will implement needed functionalities to deliver OPNFV service chaining capabilities in upstream projects including:
 +    * OpenDaylight
 +    * OVS
 +      * OpenDaylight'​s SFC project is driving changes to OVS for NSH encapsulation.
 +  * The OPNFV Service Chaining Project will deliver: ​
 +    * Documentation describing how to leverage these functions in the OPNFV platform.
 +    * Release documentation.
 +    * Required configuration files for each release.
 +    * Test cases to validate documented features.
 +==== Proposed Release Schedule ====
  
-In the first release ​we will lay the ground work for a more substantial development effort. We will leverage the Getting Started Project and investigate how NSH [[https://​tools.ietf.org/​id/​draft-quinn-sfc-nsh-04.txt]] can be used in Openstack networks, what changes would be needed and how to best implement them.+  * OPNFV SFC functionality is expected to be provided as part of OPNFV release ​2
  
-===== Proposed Release Schedule: ===== 
  
-OPNFV R1.0 timeframe of 1H 2015. 
  
network_function_chaining.txt · Last modified: 2015/05/06 20:12 by Daniel Farrell