Topic Leader(s)
Topic Overview
ETSI NFV has progressed significantly in the recent time in the concepts for management and orchestration of containerized VNFs (CNFs).
The work on modelling containerized workloads is moving to protocol stage and the concept for automated management of clusters is being shaped.
This technical presentation will introduce the concepts and specification in ETSI as well as implementation aspects from ONAP to help for alignment with RA2.
Slides & Recording
Slides are available:
Recording:
Minute
Q1: In what group is the container networking study done?
Answer: in the IFA group, the report will be IFA038, part of FEAT19, see link on last page.
Q2: Will ETSI specify in stage 3 how CISM manages the CIS cluster and CIS instances.
Answer: ETSI will not specify things already available in open source, but just map the requirements in the profiling.
Q3: Is CISM part of the infrastructure?
Answer: ETSI doesn't restrict implementations how/where CISM is to be implemented. Therefore CISM can be implemented as part of the infrastructure,
or there can be products combining the CISM with the VNFM. Everything will be described as much as necessary to support the interoperability.
Comment: Kubernetes also provide App management which is not part of CISM, but rather part of VNFM.
Q4: Will ONAP APIs change for the support of containers?
Answer: Main enhancements are within the Service Orchestrator (SO), but also the SDC needs enhancements to let it know the package includes Helm charts. W.r.t APIs, the SOL003 adaptor may need to be enhanced, no other major changes are identified.
Q5: What is the relation between ONAP and CIR?
Answer: the CIR is outside the scope of ONAP and contains the binaries while ONAP needs other information and references to the CIR.
Q6: Is an external VNFM mandatory?
Answer: In the ETSI alignment use case, an external VNFM is mandatory, but in other use cases (e.g., multi-cloud enhancement), it's not.
Q7: What about multiple VNFMs?
Answer: Currently there is no plan to support it.
Q8: Where is MANO in the diagram?
Answer: The SO implements part of MANO, also the VNFM (outside ONAP) is part of MANO.
2 Comments
Pankaj Goyal
Great presentation. Getting into the weeds: 1. Some confusion w.r.t. interaction between Service Orchestrator (SO), VNFM, VIM and CSM – VNFM required (as I understood it based on the Q&A but not required in multi-cloud. 2. w.r.t. A&AI, does it also concern itself with resources allocated to clusters? Does it interact with CISM?
Xu Yang
Hi, here's some clarifications: