OPNFV Edge Cloud strategy Task Force meeting notes: https://etherpad.opnfv.org/p/tsc_edge_cloud
...
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 |
General Recommendations
- Messaging to ensure OPNFV is viewed as relevant to Edge and solving Edge Cloud problems
- Dashboard and metrics?
- Unified view of Edge use-cases, requirements and features across projects
- Need strong collaboration with Upstream Edge communities and activities
- Open Stack
- ?
- Gambia
- At least one Edge Cloud scenario (consider both NFV and non-NFV use-cases)
- At least one Pharos Edge spec (multi-architecture)
- Set of Edge related functional test cases
- 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
Opens and Gaps
Gaps in OPNFV Projects
- ?
ETSI MEC
- Should OPNFV consider a scenario with ETSI MEC upstream implementation (e.g. NEV SDK)?
...