1 of 8

�EMCO- Project Health Check

March 29, 2023

​

2 of 8

Agenda

  • Recent Community Shift & Current Community Status
  • Paths Forward
  • What is EMCO asking from the TAC?

3 of 8

Recent Community Shift & Current Community Status

  • Intel has decided to pull back from EMCO
  • Intel is/was the primary code contributor to EMCO
  • Aarna Networks has stepped up to take the lead on EMCO

​

​

4 of 8

Paths Forward

  • Architecturally EMCO and Nephio can coexist as shown in slide 5
  • There is potential to upstream some existing code to Nephio per (more on slide 6).
  • Near-term/Short-term EMCO activities will focus on:
                  • Support
                  • Patch releases for bugs, security, observability, compatibility
  • The community recommendations to keep EMCO as a sandbox project. This will not force the project one way or another and lets the project run its natural course while also giving the community the opportunity to move onto other directions without making a hard decision at this time.

​

5 of 8

Synergy with other OSS/SDO projects

Open APIs

Open APIs

  • ONAP end-to-end service orchestration layer can interface with Nephio using open APIs for domain automation for a) cloud infrastructure b) Network function automation using Kubernetes Resource model (KRM) /Configuration-as-Data based automation.
  • EMCO is another opensource in LFN,�that can interface with Nephio for KRM/CaD based automation of a) cloud infrastructure b) Network function automation but it is optional.
  • Kubernetes is part of CNCF and fundamental to Nephio. Nephio further expands K8s CRDs/Operators for telecom automation use cases.
  • Nephio CRDs are in conformance with O-RAN and 3GPP specifications.

ONAP External API

ONAP Service Orchestration

Configuration (CDS)

EMCO

​

​

Service Assurance

(DCAE, Policy, A&AI)

​

​

Nephio

On Premise infrastructure

Public Cloud Infrastructure

Nephio

ONAP Component (Module Name)

EMCO

CNF

CNF

CNF

CNF

CNF

CNF

Standards based

REST Client, GUI

​

​

Open APIs

Open APIs

EMCO

​

​

EMCO

​

​

6 of 8

Options For EMCO Contributions To Nephio

  • EMCO can provide a tool to convert Helm charts to Nephio CRDs, either by itself or as a higher-level orchestrator.
      • Nephio has plans for a Helm conversion tool. Need to collaborate.
  • EMCO can contribute placement, action, Istio, Open Policy Agent, Temporal, and Hardware Placement Awareness (HPA) controllers for application orchestration (at least the concepts, if not the code).
  • EMCO can contribute automation for certificate management, with or without a service mesh like Istio.
  • Edge Relocation code from Orange.

​

7 of 8

What is EMCO asking from the TAC?

  • Feedback
  • Any addition options

8 of 8

Backup

​