...
- EMCO/ONAP Architecture alignment Deep Dive – 3 hours
- 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)
- Part 2: Appropriate use cases for EMCO and ONAP, when to use them separately and or together
- Part 3: Post-onboarding activities and requirements as products move into production – Day 2 – Post-onboarding – Day N – where and how are ongoing metrics collected and how to they feed into relevant parts of the stack....
- What is considered in or out of the stack in various architectures....
- Part 34: Interoperability Challenges CNF Interoperability Challenges between workload/platform and orchestrator/workload
- CNI – is this the only answer?
- Other networking frameworks (eg., Istio, Envoy)?
- Networking abstraction – how do we push this past the goal line, publish, and test?
- Data Plane
- If performance tuning is a source of interop issues, how do we address these?
- Are data plane issues as opaque to workloads as claimed (should we do a survey, or testing experiment to have non-anecdotal data)?
- Part 1: On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
...