...
- Contributions towards Architecture (closely interface with architecture subcommittee)
- Architecture for Multi-tenant Edge Cloud Domain which Domain
- Which can support several Edge locations with different
- Workload profiles
- that enable Telco VNFs, Third party workloads, MEC, IoT and other application workloads etc.
- Infrastructure profiles that enable Distributed, Highly-secure, Config/Cloud-diverse, Capacity-constrained and Performance/Isolation-aware network functions and application workloads.
- Hierarchical ONAP Central/Edge Architecture to support aforementioned IaaS/PaaS Intent-based APIs.
- Architecture for Service Assurance addressing a large number of edge clouds.
- Leverage Cloud Native Transformation
- in a heterogeneous cloud environment
- This work will be immediately beneficial to ONAP supporting deployment of containerized VNFs, since the edge cloud requirements are a super-set of general data center requirements.
- ONAP <-> Multi-tenant Edge Cloud Domain
- Hierarchical ONAP Central/Edge Architecture including closed-loop service assurance
- Contributions towards Functional Requirements per Release (closely interface with use case subcommittee)
- ONAP <-> Multi-tenant Edge Cloud Domain IaaS/PaaS Intent-based APIs and Context (e.g. summarized telemetry information) APIs
- Contributions towards Functional Requirement realization (closely interface with all ONAP projects)
- Working closely with other key edge related open source initiatives
- Joint Architectural (APIs etc.) discussions
- Joint demo planning for conferences
- ONAP Network Service <-> External Edge Open Source initiatives value add APIs
- Examples - Proximal placement of MEC App and 5G CU-UP VNF for delivering ultra-low-latency services
...