User Tools

Site Tools


requirements_projects:openstack_based_vnf_forwarding_graph

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
requirements_projects:openstack_based_vnf_forwarding_graph [2015/02/17 17:28]
cathy zhang
requirements_projects:openstack_based_vnf_forwarding_graph [2015/09/09 18:46] (current)
cathy zhang [Names and affiliations of the committers:]
Line 7: Line 7:
 ==== Project description:​ ==== ==== Project description:​ ====
  
-This project provides a framework for automatic and rapid deployment of end-to-end VNF services through VNFFG, which is one of the NFV components documented the ETSI NFV Management and Orchestration (MANO) specification [NFVMAN001]. ETSI GS NFV specification also dedicates a specific section (section 6) to VNFFG based network services. VNFs and VNFFGs are also known by the terms Service Function (SF) and Service Function Chain (SFC) respectively.+This project provides a framework for automatic and rapid deployment of end-to-end VNF services through VNFFG, which is one of the NFV components documented ​in the ETSI NFV Management and Orchestration (MANO) specification [NFVMAN001]. ETSI GS NFV specification also dedicates a specific section (section 6) to VNFFG based network services. VNFs and VNFFGs are also known by the terms Service Function (SF) and Service Function Chain (SFC) respectively.
  
 This project proposal will bring in ongoing OpenStack work on VNFFG and ONF OpenFlow work on service chaining. It also includes integrating OpenStack SFC related components with different vendors’ VNFs instantiated on virtual machines. This project will create a link between OpenStack, ONF OpenFlow, and OPNFV. The diagram below shows an end-to-end service provided by a VNFFG consisting of a number of VNFs. This project proposal will bring in ongoing OpenStack work on VNFFG and ONF OpenFlow work on service chaining. It also includes integrating OpenStack SFC related components with different vendors’ VNFs instantiated on virtual machines. This project will create a link between OpenStack, ONF OpenFlow, and OPNFV. The diagram below shows an end-to-end service provided by a VNFFG consisting of a number of VNFs.
 +
 +  * VNFFG Architecture Slides: ​
 +  * Requirement:​ https://​etherpad.opnfv.org/​p/​vnffg_requirement
 +  * Project specification: ​
 +  * Blueprints: https://​etherpad.opnfv.org/​p/​vnffg_bps
 +  * [[https://​wiki.opnfv.org/​meetings/​vnffg|Meeting Info]] ​
  
    
 ==== Scope: ==== ==== Scope: ====
  
-This goal of the project is to demonstrate an OpenStack based and OpenFlow compliant solution which will dynamically set up VNFFG so that different tenants’ flows can be steered through different sequence of VNFs. +The goal of the project is to demonstrate an OpenStack based and OpenFlow compliant solution which will dynamically set up VNFFG so that different tenants’ flows can be steered through different sequence of VNFs. 
 The diagram below shows the VNF Chaining Architecture which is in line with Figure 4 in the ETSI NFV Architecture [NFVSWA001] and ONF Service Chain Architecture [ONF-SFC]. ​ The NFV VNFFG architecture consists of the OpenStack-based VNFFG Manager, multiple OpenFlow based SDN Controllers,​ and other components in the NFV infrastructure such as the Traffic Classifiers hosted on the Server, the Service Function Forwarders hosted on vSwitch and the Service Functions running on VMs. The diagram below shows the VNF Chaining Architecture which is in line with Figure 4 in the ETSI NFV Architecture [NFVSWA001] and ONF Service Chain Architecture [ONF-SFC]. ​ The NFV VNFFG architecture consists of the OpenStack-based VNFFG Manager, multiple OpenFlow based SDN Controllers,​ and other components in the NFV infrastructure such as the Traffic Classifiers hosted on the Server, the Service Function Forwarders hosted on vSwitch and the Service Functions running on VMs.
  
 The interfaces between these virtual devices include the management plane interfaces, the control plane interfaces, and the data plane interfaces. The interfaces between these virtual devices include the management plane interfaces, the control plane interfaces, and the data plane interfaces.
-{{ requirements_projects:​opnfv_sfc_proposal_architecture_diagramv1.png?700 |}}+{{ requirements_projects:​opnfv_sfc_proposal_architecture_diagram v1.png?700 |}}
    
 === Components ==== === Components ====
Line 90: Line 96:
   * [SFC-SCH] ​  IETF Service Chain Header draft-zhang-sfc-sch-02   * [SFC-SCH] ​  IETF Service Chain Header draft-zhang-sfc-sch-02
  
 +===== Key Project Facts =====
 +
 +** Repo name: ** vnf_forwarding_graph \\
 +** Project Category: ** requirement\\
 +** Lifecycle State: ** \\
 +** Primary Contact: ** cathy.h.zhang@huawei.com \\
 +** Project Lead: ** cathy.h.zhang@huawei.com \\
 +** Jira Project Name: ** vnf forwarding graph\\
 +** Jira Project Prefix: ** vfngraph \\
 +** mailing list tag ** [vnfgraph]\\
  
 ==== Names and affiliations of the committers: ==== ==== Names and affiliations of the committers: ====
   *  Cathy Zhang, cathy.h.zhang@huawei.com   *  Cathy Zhang, cathy.h.zhang@huawei.com
   *  Louis Fourie, louis.fourie@huawei.com   *  Louis Fourie, louis.fourie@huawei.com
 +  * Weidong Shao, weidong.shao@huawei.com
   *  Eugene Yu, yuyijun@huawei.com   *  Eugene Yu, yuyijun@huawei.com
   *  Dave Lenrow, david.lenrow@hp.com   *  Dave Lenrow, david.lenrow@hp.com
   *  Srini Addepalli saddepalli@freescale.com   *  Srini Addepalli saddepalli@freescale.com
-  *  Jeff Maguire (Freescale) 
   *  Nicolas Bouthors, Nicolas.BOUTHORS@qosmos.com   *  Nicolas Bouthors, Nicolas.BOUTHORS@qosmos.com
-  *  Li Chen (China Mobile) 
   *  Kevin Glavin (Riverbed)   *  Kevin Glavin (Riverbed)
   * Balaji P balaji.p@freescale.com   * Balaji P balaji.p@freescale.com
Line 109: Line 124:
   *  Linda Dunbar (Huawei)   *  Linda Dunbar (Huawei)
   *  Myo Zarny (Goldman Sachs)   *  Myo Zarny (Goldman Sachs)
 +  * Weidong Shao (Huawei)
  
 === Feature List === === Feature List ===
Line 119: Line 135:
   * SCH encapsulation mechanism for chain-ID and metadata in the data plane.   * SCH encapsulation mechanism for chain-ID and metadata in the data plane.
   * Service by-pass feature which can dynamically bypass a VNF in the case that the VNF service is not needed anymore.   * Service by-pass feature which can dynamically bypass a VNF in the case that the VNF service is not needed anymore.
- 
 ==== Planned Deliverables ==== ==== Planned Deliverables ====
  
Line 134: Line 149:
 ==== Proposed Release Schedule: ==== ==== Proposed Release Schedule: ====
 May 2015 or aligned with OPNFV release. May 2015 or aligned with OPNFV release.
- 
requirements_projects/openstack_based_vnf_forwarding_graph.1424194103.txt.gz · Last modified: 2015/02/17 17:28 by cathy zhang