Topic Leader(s)
Topic Description
75m, Ranny Haiby
Topic Overview
- MCO/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.
- MCO/ONAP Architecture alignment Deep Dive
Slides & Recording
Agenda
Awesome presentation
- Point 1
- Point 2