...
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
CNF Support
- CNF Support is one of Ericsson’s highest priority work items for ONAP
- Define a fast path to CNF support, and accomplish it across multiple releases (Honolulu+)
- For now, leverage currently available ETSI Stage 2 specifications, without just waiting for ETSI Stage 3 (SOL)
- Many (Ericsson, Verizon, Bell Canada, Huawei, others) believe the target is CNF, 5G Edge, etc. VNF support is a steppingstone towards that goal
- CNF support and Cloud Native Support are closely related.
- CNF enables Cloud Native (Microservices, Containers, Elastic scalability, On-demand deployment)
- What other Cloud Native support? APs: Define its scope and study architecture
- In Honolulu, CNF scope is:
- CNF modeling and distribution support for microservice-based CNF and images,
- CNF LCM through SO, SO NFVO (or VFC) and VNFM via standard APIs (covering instantiation and Day 0 configuration based on Helm Charts)
- Note: VNFM support for CNF is vendor-specific
- OOF-based Granting only for both VNF/CNF Instantiation and Termination, not for VNF/CNF Healing or Scaling
- SoftwareImagesandContainerImageHandlingsviaNFVO,ETSICatalogManager and CIR
- Collaboratewithnon-ETSI-basedCNFsupportinSO;SO launches the CNF LCM path based on models (i.e., model-driven)
...