Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
==== Project Name: ====

  * Proposed name for the project: edge nfv
  * Proposed name for the repository: enfv
  * Project Categories: Requirements

==== Project description: ====
  * The NFV movement is largely focused gaining the efficiencies of large data centre compute infrastructure. This is sensible, however to paraphrase the old switching/routing saying ... centralize what you can, distribute what you must. Some applications naturally belong at the edge: WAN Acceleration, Content Cacheing, and depending on your philosophy, Firewalling all fall into that category. Other more specialized test applications also need to be at the edge to exercise the portions of the network under test. Similarly many business applications are most efficiently delivered at the edge. 

  * The purpose of this Requirements Project is to articulate the capabilities and behaviours needed in Edge NFV platforms, and how they interact with centralized NFVI and MANO components of NFV solutions
    * Appropriate Tunneling for User Traffic across WAN (Ethernet, IP/MPLS) links
    * Appropriate Tunneling for Management Traffic across WAN links 
      * Including reachability requirements to the compute platform
    * Extending Multi-DC management to address many small "DC" locations
    * Monitoring Capabilities required for a remote Compute Node
    * Squaring Bare Metal with remote survivability and whether IaaS is more appropriate for remote locations


  * Include any architecture diagrams or specifications, reference to OPNFV requirements list.

[[https://wiki.opnfv.org/_media/project_proposals/opnfv-edge-nfvi.pptx]]

==== Scope: ====

  * This is a requirements project, therefore it is proposed to develop use cases, requirements, as well as upstream project blue prints and associated test cases. 

==== Dependencies: ====

  * Identify similar projects is underway or being proposed in OPNFV or upstream project
    * Pharos project, Doctor project, Promise project, DPACC project, LAR-E project
  * Identify any open source upstream projects and release timeline. 
    * OpenStack, Open Daylight, OVS


==== Committers and Contributors: ====

Committers:
  * James Buchanan - jbuchanan@advaoptical.com - Project Lead
  * Qiao Fu - fuqiao@chinamobile.com
  * Michael Kloberdans - m.kloberdans@cablelabs.com
  * Prayson Pate - Prayson.Pate@overturenetworks.com
  * Jesse Hong - Jesse.Hong@huawei.com
  * Ludwig, Michael - Michael.Ludwig@spirent.com


Contributors:
  * John Berg - j.berg@cablelabs.com
  * Andrew Sergeev – asergeev@advaoptical.com
  * Ross Cassan – ross.cassan@spirent.com
  * Tomasz Remiszewski - TRemiszewski@advaoptical.com
  * Diego LozanodeFournas - Diego.LozanodeFournas@spirent.com
  * Jun Zhang - zhang.jun3g@zte.com.cn
  * Yang Jian - yangjianyjy@chinamobile.com
  * Jinghai Li - li.jinghai3@zte.com.cn
  * Kevin Luehrs - K.Luehrs@cablelabs.com
  * Bharat Mota - bharat.mota@freescale.com
  * John Myla - johnmyla@freescale.com
  * Kevin Canady - Kevin.Canady@spirent.com
  * Waqar Kahn - w.khan-contractor@cablelabs.com


 
==== Planned deliverables ====

  * Documentation and mindshare necessary to advance to the next stage of the project lifecycle.

==== Proposed Release Schedule: ====

  * We plan on taking 6 months to complete this phase.
Wiki

User Tools

Site Tools

Page Tools
