Page tree
Skip to end of metadata
Go to start of metadata

Project Name:

  • Proposed name for the project: Reference platform design for edge cloud in OPNFV
  • Proposed name for the repository: edgecloud

Project description:

With the emergence of 5G and other technologies, new services with high throughput and low latency, such as AR/VR, automatic drive, etc., make edge cloud an important rising scenario for Telco Operators. The so called edge clouds may include customer premises equipment, access-level DC, county-level DC and municipal-level DC. Multiple new services and applications from both telco operators and 3rd party companies will be deployed at the edge to enable new services and enhance customer experience. Therefore, operators have to re-design or reconstruct their edge central office to deliver these diversified new services, and in the meantime reduce their CAPEX and OPEX. Edge clouds share a similar but simplified NFV+SDN architecture as the core DC but has more implementation constraints and complexity due to limited physical space and power, more distributed heterogeneous environments and stricter service requirements.

Carrier-scale edge cloud has the following features:

  • Limited physical DC environment: limited space and power resource
  • Remote & scattered location: closer to the users, unattended O&M
  • Large amount: tens of thousands of edge cloud sites scattered all over the country, while the number of core sites are less than a hundred
  • Small scale: less than 10 in AP possible
  • Special traffic-forwarding/processing services require acceleration: low-delay, high-bandwidth services such as MEC, CDN, 5G-UPF
  • Resource heterogeneity: various infrastructures including VM, container and bare metal

These features lead to a bunch of requirements of architecture of edge cloud, which requires specific design. In the meantime, we also hope the architecture of edge should stay as close to core as possible, so that we could maintain the whole network, from core to edge, in a unified way.

This project will focus on a Reference Platform for edge cloud, and is intended to output a limited number of scenarios specifically designed for edge, which will meet the varied requirement from End Users.


1) Requirements analysis.

  • Analyze and conclude the requirements of multiple edge services (MEC, CRAN, vCPE, vOLT, vCDN, etc.)
  • Translate edge-service requirements into deployment requirements including NFV/SDN component requirements (NFVO, VNFM, VIM, Hypervisor, VSW, HW, etc.)
  • Guide evolution of Pharos specification suitable for edge cloud scenarios. 

2) Scenario design

  • Define and release a limited number of scenarios for edge cloud taking consideration of the analyzed requirements

3) Upstream collaboration

  • Collaborate with OpenStack, ONAP, Akraino, ODL and other related community for requirements analysis and scenario design
  • Output detailed requirements for components to relevant project/s.

4) Testing strategy

  • Define and develop test strategy and test cases for edge specific testing (e.g. low latency requirement of the stack in edge, performance in specific edge scenarios, and etc.)
  • Tests developed may also be used by Dovetail if OVP is extended to include edge platforms.


  • The project will focus on design and development of reference platform of edge cloud in OPNFV.
  • Scope includes NFVI, VIM, MANO.
  • The scope excludes developing edge VNFs or Apps.


  • OPNFV CI/CD and testing methodologies will be extended with use cases specific to the types of edge stack that has been defined by this project


  • Requirement analysis for edge cloud
  • Architecture design for edge cloud
  • Scenario description for edge cloud
  • Upstream analysis for edge cloud


  • It’s expected that some opensource and standard projects will be used to drive the deployment of edge cloud. The edge cloud project will seek to leverage standards-based and open-source that can be integrated into OPNFV edge solutions.
  • Related OPNFV projects
    • DPACC
      • Cooperate with DPACC project in edge cloud usecases. Integrate the acceleration architecture degined DPACC into edge scenarios. Test the specific scenarios to see if the DPACC acceleration architecture can meet the edge cloud requirement
    • Clover
      • Cooperate with Clover project on edge VNF containerization. It can be foreseen future edge will include app deployed as containers. It is necessary to work with clover project to work out the detailed requirements and architecture for containerized app deployed in edge.
    • Container4NFV
      • Collaborate with the container4NFV project on edge scenarios. Making sure the edge cloud will coordinate with both K8S and Openstack.
    • Auto
      • Collaborate on the edge scenarios. Integrated with ONAP to realize the edge cloud orchestration. Work out the orchestration schema of ONAP with both VM and container in scope
  • OpenStack
    • Cooperate with OpenStack community especially the edge computing WG to verify and explore more on remote management like multi-region, cell and so on.  Cooperate with Cyborg project to help the acceleration in edge cloud.
  • ONAP
    • Cooperate with ONAP to realize the orchestration of edge scenarios and global orchestration.
  • Akraino
    • Cooperate with Akraino with edge cloud reference platform. Output platform design and integrated scenarios to Akraino and reduce vendor-lock in for edge cloud.


fuqiao <>  Requirement and architecture design for edge cloud
Beth Cohen -- Requirements and architectures for federated Edge Cloud
Adrian Peret - Requirements and architecture for edge cloud
Azhar Sayeed - - Requirements and Architecture for Edge
Julien <> - Architect of NFV
Jingbo Hao <> Requirements for edge cloud
Gergely Csatari <> Reguirements and architecture
Ildiko Vancsa <> architecture and cross-community liaison
Trevor Cooper <> architecture and Akraino liason
Cristina Pauna <> Scenario definition and implementation
Xiaohua Zhang <> Requirement and architecture
Deepak S <> - edge workload analysis 
Qihui Zhao<> -- Requirement and architecture
Yamei Fan<> architecture


[SMJ] Syed Moneeb Javed <>
Pasi Vaananen <> requirements & architecture

Azhar Sayeed <> requirements and architecture
Kin-Yip Liu <>
Paul-Andre Raymond <>

Planned deliverables (Outputs):

  • Requirement for edge cloud
  • Architecture design for edge cloud
  • Typical integrated scenarios for edge cloud
  • Upstream analysis
  • Test case for edge

Proposed Release Schedule:

  • First release in G release (if possible)

Related discussion links and slides

Project Proposal slides

20180502_Edge Cloud_requirement.pdf

Key Project Facts

Project Name: Reference platform design for edge cloud in OPNFV
Repo name: Edgecloud
Lifecycle State: Incubation
Primary Contact:
Project Lead: TBD
Jira Project Name: Same as Project name 
Jira Project Prefix: Edgecloud
mailing list tag [Should match Jira Project Prefix] 



  • No labels


  1. Perhaps you could add VCO & CRAN projects on to-coordinate with list, as both are specifically focused on building infrastructure to support edge use cases (CRAN for RAN, and VCO in larger overall architecture and building specific use cases to learn what works and what needs improvement)  ? 

  2. Between LF and ONF we have different projects with pretty much the same goal. VCO and CORD, very similar, with some different components. CRAN. Now Edge Cloud. 

    It seems to me a very inefficient way to utilize resources.  Community effort should be channeled properly, especially considering ONF is a member of OPNFV and cooperation in this matter should be easily achievable.

  3. I fully agree with you, at large we have at least (just quick:

    • OPNFV edge proposal (in addition older edge project), 
    • ONF ONOS+CORD variants, 
    • OpenStack edge projects
    • ONAP edge / edge use cases projects, 
    • TIP vRAN/ORAN, 
    • xRAN-->ORAN
    • TIP Edge/MEC, and
    • Akraino

    And that is not mentioning huge number of projects that have edge uses / relevance without specific focus on edge (alone) or many IoT focused projects which have "edgy" aspects. Working together, we could likely get there faster. But, there are differences on approaches in terms of technology stack selections, which would require someone give up their pet projects, so in practice it may be hard to get to smaller number.

    Any ideas on how you would propose to accomplish such consolidation / consensus at least to reduce fragmentation (please don't say that we'll just pick THE winner) ?

    1. (smile) No, just pick the winner doesn't solve the fragmentation problem. 

      I need to check the ways of working of OPNFV, but at least within OPNFV there should be a project approval mechanism that verifies there are no other similar projects already ongoing. The Technical Steering Committee should look into this and reroute resources appropriately, if required. 

      Between OPNFV and ONF it may be a bit more tricky, but same principle should apply.

      By the way, on the topic:

  4. Not to mention the Multi-Access Edge and Edge NFV in OPNFV alone..

    Agreed that we should look in the least to consolidate the OPNFV projects


    1. Thank you for all your comments for this project. I actually see this project as a complimentary for all the other existing and active projects in OPNFV, and could possibly cover the gaps currently exist for edge related work in OPNFV. 

      This project would working on the overall architecture design for edge and would focus on reference platform for edge. Our initial goal is to output a few specific scenarios that would target edge usecase.

      for vCO, it is not exactly a project in OPNFV but rather a demo which purpose from my understanding is to showcase the capability for OPNFV platform, while vCPE and CRAN are the use case we choose to show. We can't rely on a demo to help drive the progress of edge reference platform in OPNFV.

      for CRAN, what we see is an application that will run on edge cloud, together with other applications including MEC, vCDN, and etc.. I expect this project can help provide requirement for edge stack including hardware and edge stack, but could hardly rely  on it to work out the reference platform.

      for multi-access edge project, it is only a proposal for now. and before proposing this new project, I actually reached out to the proposal owning, Bryan Sullivan, and he claimed he will not continue proposing this project. so we possibly will have to consider this proposal dead some how

      for the edge NFV project, I actually is one of the committer for that project when it is active two years back. This project focusing more on the vCPE applications deployed on edge. However this project is not active for two years. if you are familiar with the projects in OPNFV , you will find this project as some how dead as well. I also reached out to the project owners, and they claimed their interest has shift and can't find new contributors. 

      Hope this will answer some of your questions.