- OPNFV Edge Cloud strategy Task Force meeting notes: https://etherpad.opnfv.org/p/tsc_edge_cloud
- Edge Cloud Task Force Conclusion reportEdge Cloud WG conclusion report
Recommendations
- Develop clear messaging to establish and reinforce OPNFV relevance and unique role in the Industry to address challenges with integrating, deploying, testing, managing Edge Cloud.
- Provide a unified view of OPNFV Edge activities to help projects collaborate and avoid duplication
- Maintain an "Edge dashboard" or equivalent tool to track progress and community artifacts for Edge
- Consider publishing a White Paper and/or joint conference sessions highlighting collaboration with upstream projects
- Develop a roadmap of Edge announcement/s (ONS in September?)
- TSC to actively encourage and facilitate OPNFV Edge activities with strong developer focus (beyond requirements and use-case analysis)
- Need a code base for developers to work on and focus community effort
- Need an installer strategy for Edge Cloud deployment (Compass?)
- Establish strong collaboration with relevant upstream communities and Edge related Industry activities
- EdgeCloud has already established a working relationship with Open Stack Edge Computing Group (note this is being merged with FEMDC) and is exploring collaboration with Keystone and Glance
- Explore collaboration with StarlingX as upstream ingredient for first Edge scenario
- Collaborate with StarlingX, Airship, OpenStack Computing Group, etc. for Pharos spec. additions
- Solicit feedback from EUAG for validating approach and tracking progress
- Deliver at least one Edge Cloud scenario for Gambia (consider both NFV and non-NFV use-cases)
- Pharos Edge spec (first iteration, multi-architecture)
- Edge test cases
- OVP (Compliance Program)
- Develop profile of Edge platform capabilities
- Develop set of Edge relevant test cases based to test against commercial platforms
- Include Edge test-cases in release after Gambia
- Pharos
- Expand Pharos spec to n Edge flavors
- OpenStack Edge Computing group - 1) small, 2) medium
- Airship 1) Minimal (fully embedded), 2) small DC (enterprise edge, Access level CO/DC with limited space and power), 3) large (Metro level CO/DC)
- StarlingX 1) EdgeSX 2) Edge 3) Core
- etc.
- Definitions and terminology ... expand PDF?
- Support heterogeneous hardware within a POD
- Investigate feasibility to adopt ENOS framework for simulating distributed clouds
- Expand Pharos spec to n Edge flavors
8. Maintain list of perceived gaps in upstream projects wrt Edge and OPNFV activities contributing to resolving these gaps
9. Develop OPNFV position wrt ETSI MEC and how it maps to OPNFV
OPNFV Edge Cloud Activities
Note:
- Edge NFV (eNFV) project was approved in 2015 but has not been active. Project was terminated by the TSC on 5/8/2018
- Multi-access Edge project proposal has been withdrawn
Survey of OPNFV Edge Cloud activities https://etherpad.opnfv.org/p/tsc_edge_cloud_project_questions, https://etherpad.opnfv.org/p/tsc_edge_cloud_opnfv_activities
| Project or activity | Edge focus (e.g. ingredients, requirements, ...) | Hardware aspects | Test framework. Edge specific test-cases. | Upstream collaboration | Suggestions | |
|---|---|---|---|---|---|---|
| Auto | ONAP-based automation of VNF management with Edge Cloud use-case | Management of Edge Cloud vCPE | Compare power consumption of architectures | Functest initially only functional tests. Later include performance monitoring with ONAP Data Collection Analytics and Events | ONAP Edge automation | |
| EdgeCloud | requirement analysis architecture design reference platform for edge | TBD | is working with pharos for edge specific hardware | TBD | openstack EC WG |
|
| Container4NFV | Container4NFV provides basic CT feature for VNF, for example. It supports mutlus, DPDK, and SR-IOV. In edge , container is the best tool which can reduce the resource usage. | No | In Container4NFV, we support x86 and ARM. In order to accelerate data plane, containe4nfv support DPDK and SR-IOV. In future, we will support VPP. | Project specific testing for yardstick. test the network performance ,including DPDK, SR-IOV and VPP. but not specific for edge |
| |
| CRAN | Concluding the MEC applications for radio access network, exploring the deployment proposal for MEC and 5G CU. For the specific design. | TBD |
| |||
| Clover | Edge is a scenario for cloud native support. Focus is on service mesh (micro-services) using containers managed by Kubernetes. | 5G low latency services, AR/VR, IoT | Select edge devices, will contribute an edge pod to Pharos (with K8S and container support). | Extend CI to zero-touch continuous deployment. Developing Edge test cases for various Cloud Native test tools. Planning performance testing. | ONAP ( pending discussion), k8s, CNCF |
|
| VCO Demo 2.0 (Is a PoC, not run as a project) | Central Office Edge. Mobile network access (vRAN) and scope includes virtualized mobile core network components. "Learn by doing" approach and gap analysis using commercial and open source VNFs. | A set of mobile network specific services | Using community contributed/supported hardware as demo, not on a Pharos POD. For future may use hardware from e.g. OCP, TIP, others? | No edge specific test cases. Testing is not a focus. | ONAP Casablanca (not committed to yet). Also Open Stack, ODL, k8s, OpenAirInterface |
|
Upstream Edge Cloud Activities
Survey of upstream Edge Cloud activities https://etherpad.opnfv.org/p/tsc_edge_cloud_upstream_communities
| Upstreams | Edge related activities | useful link | progress | collaboration with OPNFV | suggestion for next step |
|---|---|---|---|---|---|
| ONAP | Edge automation WG | https://wiki.onap.org/display/DW/Edge+Automation+through+ONAP | Regular meetings some discussion for vCPE and MEC Edge automation working group focusing on Edge Cloud for Casablanca (3rd release Nov 15th) ... 1) Add hierarchical orchestration 2) Extend hardware platform awareness, Provide a way to select the best region to place dynamic apps | Not yet. Hope the connection could be built with AUTO and Edge cloud project to address Orchestration issue of edge |
|
| OpenStack | Edge computing WG start in 2017 Fog/Edge/Massively Distributed Clouds SIG (these two groups plan to combine) | https://www.openstack.org/edge-computing/ https://www.openstack.org/assets/edge/OpenStack-EdgeWhitepaper-v3-online.pdf https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds Glance image handling in edge environment : https://wiki.openstack.org/wiki/Image_handling_in_edge_environment Keystone edge architectures: https://wiki.openstack.org/wiki/Keystone_edge_architectures | white paper publish for edge from the EC WG discussion of EC WG mainly focusing on security of edge, Keystone, Glance. Not to redesign OpenStack from scrach for edge, but to made certain modification to have openstack fit into edge | Collaboration activity is already underway with the OPNFV Edge Cloud project. |
|
| Akraino (LFN) | Fully integrated edge stack with production quality code and blue-prints including hardware specs. | Akraino 1.0 release definition, Blueprints definition, use cases .... brainstorm from May F2F https://etherpad.acumos.org/p/Akraino-release Mailing lists https://lists.akraino.org/g/main | Governance and membership/process structures WIP Currently no seed code Definition of deliverables are WIP ... "blueprints", developer APIs, middleware (SDKs), ETSI MEC functions and APIs | OPNFV has mature CI/CD Infra, test frameworks and release engineering tools/process which could be leveraged by Akraino. OPNFV EdgeCloud is developing requirements which could be consumed by Akraino. Akraino help define OPNFV Edge Cloud scenarios and Pharos Edge flavors (from Blueprints). Monitor progress and evaluate collaboration opportunities once Akraino roadmap is clear. |
|
| Airship (OSF) | ATT "Oceans" seed code for deployment of "under cloud" | OSF project, still forming, some seed code available | Monitor for now and reevaluate opportunities for collaboration once project is established. | Consider site definitions (from ATT) for Pharos Edge spec | |
| StarlingX (OSF) | Wind River Titanium Cloud R5 seed code. | http://www.starlingx.io/ | OSF project announced recently at Open Stack Summit. Wind River Titanium Cloud is seed code. | Possible collaboration to deploy StarlingX as an Edge scenario in OPNFV. | Consider Wind River Titanium deployment flavors for Edge POD definition. |
| Open Edge Compute Initiative (OEC) | Developing Open Edge API for 3rd party developers | Early stages, not much visible yet | OEC is setting up a “Living Edge Lab” real-world testbed for Edge Computing http://openedgecomputing.org/lel.html. Investigate possible synergies with Pharos spec/lab and overlap of use-cases in OPNFV projects. | Monitor progress. | |
| CORD (ONF) | open reference implementation of central office with commodity servers, white-box switches, open source software (e.g., OpenStack, ONOS, XOS) | Uses ONOS control plane for SDN and managing network components https://onosproject.org/ | CORD profiles available for install: | Not evaluated sufficiently for recommendation. Evaluate synergy/overlap with vCO Demo 2.0? | Assign responsibility for further investigation. |
| Kubernetes (CNCF) | Automating deployment, scaling, and management of containerized applications | https://kubernetes.io/ | v1.10 | Collaboration with the EdgeCloud project and AUTO to work out edge scenario taking consideration of container management | EdgeCloud and Auto to agree roles and next steps |
| EdgeXFoundry (LF) | IoT edge computing framework and and ecosystem of interoperable components that accelerates the API framework for enabling IoT services at the Edge | Certification program planned | Opportunity for collaboration is not clear at this stage. | Monitor progress. Investigate certification program. | |
| Telecom Infra Project (TIP) | Lab and field implementations for services/applications at the network edge | TIP Ecosystem Acceleration Centers hosted in the UK, Paris, Seoul and Germany. TIP Community Labs are physical spaces that enable collaboration between member companies in a TIP project group to develop telecom infrastructure solutions | Not evaluated sufficiently for recommendation. | Assign responsibility for further investigation. |