DRAFT
OPNFV Edge Cloud strategy Task Force meeting notes: https://etherpad.opnfv.org/p/tsc_edge_cloud
...
Survey of upstream Edge Cloud activities
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 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
...
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 |
...