...
- Summary:
- Identify architectural gaps in ONAP in satisfying edge requirements and drive those requirements in various ONAP projects.
- Deep engagement with edge related external open source initiatives to drive the above.
- Accomplishments:
- The Edge Automation through ONAP (https://wiki.onap.org/display/DW/Edge+Automation+through+ONAP) effort started as a working group in May 2018 as part of the use case subcommittee and is targeting concrete deliverables impacting multiple ONAP projects and driving the ONAP edge requirements & architecture for Casablanca and beyond. The working group has been run with its own meetings and maintaining set of wiki pages. As part of Casablanca, multiple initiatives have been taken such as supporting Kubernetes based edges, Aggregation of metrics and Cloud-agnostics way of utilizing cloud/edge site features. There is strong interest from the community in this working group and we would like transition to a subcommittee. Please find the rational below.
- Rationale for transition to subcommittee:
- Strong and consistent interest from the community in terms of attendance and contributions
- Distributed Edge Cloud is a key area of focus for operators and vendors towards 5G transformation, local breakout, ultra-low-latency MEC applications and bandwidth-intensive IoT applications
- Collaboration with other key edge related open source initiatives O-RAN Alliance, Linux Foundation (Akraino, EdgeX Foundry, IoTvity etc.), Kubernetes (Edge Working Group, Network Service Mesh, Multus, OVN etc.)
- The work needs substantial discussions and engagement with external open source initiatives to make concrete ONAP architecture recommendations realize the implementation – this is very different from other functional & non-functional requirement group which are ONAP specific
- Making it a formal subcommittee with targeted focus provides substantial visibility and can enable better ONAP internal and ONAP external participation
Challenges with independent task forces/coordinators:
Independent task forces under each one of the sub-committees (use case, architecture, security, modelling etc.) and independent external open source/standards coordinator can lead to more fragmentation of the work happening in Edge
Key Deliverables for upcoming ONAP releases:
...