...
- Proposed joint meeting with EMCO technical leaders (Sharad Mishra , Srinivasa Addepalli ) to discuss details of future integration - Roles and responsibilities, API calls, Integration points (Multicloud vs. directly from SO), any other open technical questions.
- Follow-up on analysis done by Orange - EMCO & Ongoing Work in Orange , K8s plugin - Summary and use in ONAP for CNFO
- Why was EMCO created in the first place? What were the motivations? What ONAP gaps does EMCO address?
- A few initial gaps for integration were identified by Lukasz Rajewski
- Srinivasa Addepalli - EMCOs goal is to deploy "complex" applications (or CNFs) across multiple K8S clusters. It continues monitoring the deployed applications and provides status. EMCO assumes K8S is the cloud infrastructure, but it supports VMs as well. It can communicate with public cloud APIs (Azure, GCP). EMCO v1 was integrated with ONAP multicloud, which handles single CNFs. EMCO v2 can handle a network service (multiple CNFs). EMCO does not have a "standard compliant" northbound API (e.g. ETSI VNFM or NFVO)
- Seshu Kumar Mudiganti - Proposes a Service-Orchestration/Resource-Orchestration approach. EMCO can handle Helm charts deployment (=resource). SO will handle the service level.
- Lukasz Rajewski - We should compare the terminology between ONAP/EMCO/ETSI.
- Srinivasa Addepalli - EMCO handles "composite applications" described by a Helm chart. It provides value by interconnecting the components of the composite service, e.g. using ISTIO.
- What will be the demarcation between ONAP and EMCO? Will EMCO handle an entire CNF? Each Helm chart separately? In EMCO, One application may have multiple micro services. ONAP has "services" consisting of "VF"s, That may have "VF modules". Each "VF module" is a Helm chart.
- Lukasz Rajewski - The main difference between ONAP and EMCO is that ONAP deploys each "VF module" (=Helm chart) separately, using an API call to multicloud. We need to find a way to preserve this approach, making multiple API calls to EMCO.
- First step for integration - ONAP will call EMCO for each "VF module". This will not take full advantage of EMCO's capabilities, but will only serve as a first step toward deeper integration. CNF adapter in SO will be the integration point. Multicloud will not be used for this integration.
- Future steps for integration - Have EMCO handle an entire VF as one composite application.
December 7th, 2021 at 2pm UTC
- Plan EMCO integration - PoC in Jakarta? Full feature later?
Action Items (In Progress)
...