...
- EMCO/ONAP Architecture alignment Deep Dive
- Part 1: On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
- Assumption for ingress: Helm v3
- Needs to be jointly defined first, then determine if and where it belongs upstream.
- Is there a connection to Anuket and Anuket Assured program? Infrastructure→Applications>Onboarding>MANO>Infrastructure (end-to-end)
- Appropriate use cases for EMCO and ONAP, when to use them separately and or together
- Lessons learned from:
- Magma orchestration with EMCO (2022-01-13 - EMCO: Orchestration of Magma)
- Magma orchestration with ONAP (https://wiki.onap.org/display/DW/2022+Enterprise+Task+Force?preview=/117743631/117743639/ONAP_Magma%20Integration%20status.pptx)
- Lessons learned from:
- Part 1: On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
- EMCO/ONAP Architecture alignment Deep Dive
Slides & Recording
View file | ||||
---|---|---|---|---|
|
Agenda
- EMCO/ONAP Architecture alignment Deep Dive
- Part 1: On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
- Infrastructure → Applications>Onboarding>MANO>Infrastructure (end-to-end)
- Appropriate use cases for EMCO and ONAP, when to use them separately and or together
- The teams have identified two fundamental configurations, each ideally suited for different high level use cases
- ONAP is the centralized Service Orchestrator, Service Assurance and Automation Framework, with EMCO fulfilling specific roles as a component (multi cluster support, etc)
- EMCO is the distributed edge focused Service Orchestrator, with select ONAP Service Assurance components configured as needed.
- We can draw from the following examples and other supporting material during this session to describe the rationale
- Review of the EMCO_ONAP Alignment Proposal PPT.
- Lessons learned from:
- Magma orchestration with EMCO (2022-01-13 - EMCO: Orchestration of Magma)
- Magma orchestration with ONAP (https://wiki.onap.org/display/DW/2022+Enterprise+Task+Force?preview=/117743631/117743639/ONAP_Magma%20Integration%20status.pptx)
- EMCO team overviews the rationale for, deploying an app/service such as Magma as the primary SO
- Given the different configurations , how can the 5G SBP program demonstrate and delineate the rationale for the two configurations?
- Part 1: On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
...
- LJ Illuzzi - Invite this group to the newly formed 5G Super blueprint requirements workgroup. Ranny Haiby volunteers to join the workgroup
- Bob Monkman - Work with the EMCO TSC on better communication with the EMCO community. How to avoid re-creating and do more leveraging.
- Ranny Haiby - Work with Bob Monkman as the ONAP contact point for the AI above