...
...
DRAFT
OPNFV Edge Cloud strategy Task Force meeting notes: https://etherpad.opnfv.org/p/tsc_edge_cloudDRAFT
Survey of OPNFV Edge Cloud activities
Survey of upstream Edge Cloud activities
Recommendations
- Develop clear messaging to establish and reinforce OPNFV relevance and unique role in the Industry to integrate and test Edge ingredients in order to solve challenges of deploying and managing Edge Cloud
- Provide one (unified view) of OPNFV Edge activities to help projects collaborate and avoid duplication
- Maintain an "Edge dashboard" to show progress and what has been delivered
- Consider publishing a White Paper that highlights collaboration with upstream projects
- 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
- Strong collaborations with relevant upstream communities and Edge related 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 the first Edge stack upstream
- Collaborate with StarlingX, Airship, OpenStack Computing Group on adding to Pharos spec
- Establish ongoing feedback with EUAG for evaluating progress and updating objectives
- Deliver at least one Edge Cloud scenario (consider both NFV and non-NFV use-cases) for Gambia
- Pharos Edge spec (first iteration, multi-architecture)
- Edge test cases
- OVP
- Develop profile of Edge platform capabilities
- Develop set of Edge relevant test cases based to test against commercial platforms
- Pharos
- Expand to Edge flavors
- OpenStack Edge Computing group - 1) small, 2) medium
- 1) Minimal (fully embedded), 2) small DC (enterprise edge, Access level CO/DC with limited space and power), 3) large (Metro level CO/DC)
- Harmonize on definitions and terminology. Expand PDF?
- Support for heterogenous hardware within a POD
- How to do federation, scaling, simulate characteristics of remote sites?
- Expand to Edge flavors
- Maintain list of perceived gaps in upstream projects wrt Edge and OPNFV activities contributing to resolving these gaps
- Need a position wrt ETSI MEC and how this maps into OPNFV reference platform for Edge
OPNFV Edge Cloud 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
| 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 | 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 | 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 with the edge cloud project already built |
|
| 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 Current seed code is NEV SDK however this may move into StarlingX Definition of deliverables 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). |
|
| Airship (OSF) | ATT "Oceans" seed code for deployment of "under cloud" | OSF project | 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 at Open Stack Summit | Consider Wind River Titanium deployment flavors for Edge POD definition. | |
| Open Edge Compute Initiative (OEC) | Developing Open Edge API for 3rd party developers | ||||
| CORD (ONF) | open reference implementation of central office with commodity servers, white-box switches, open source software (e.g., OpenStack, ONOS, XOS) | Under development | |||
| Kubernetes (CNCF) | Automating deployment, scaling, and management of containerized applications | https://kubernetes.io/ | v1.10 | ||
| EdgeXFoundry (LF) | IoT edge computing framework and and ecosystem of interoperable components that accelerates the | Certification program planned | |||
| Telecom Infra Project (TIP) | Lab and field implementations for services/applications at the network edge |
Recommendations
...
- Pharos Edge spec (first iteration, multi-architecture)
- Edge test cases
...
- Develop set of Edge related test cases based on desirable capabilities of an Edge deployment.
- Pharos
- Expand to Edge flavors
- OpenStack Edge Computing group - 1) small, 2) medium
- 1) Minimal (fully embedded), 2) small DC (enterprise edge, Access level CO/DC with limited space and power), 3) large (Metro level CO/DC)
- Harmonize on definitions and terminology. Expand PDF?
- Support for heterogenous hardware within a POD
- How to do federation, scaling, simulate characteristics of remote sites?
- Expand to Edge flavors
- White Paper
- Include collaboration activities between communities
- Working with OpenStack on tangible activity
Opens and Gaps
Gaps in OPNFV Projects
- ?
ETSI MEC
...