ETSI Package Management

Use Cases

• ETSI Package Management Use Case
  • SOL004 VNF/PNF/NS Package includes SOL001 VNFD/PNFD/NSD with the original vendor package
  • SOL004 VNF/PNF/NS Package Security
  • SO ETSI Catalog DB enhancement, by leveraging ETSI Catalog Management Microservice

Feature Descriptions

Epic and User Story

ETSI Package Management Architecture

The diagram depicts the package management architecture. 

1. SDC supports SOL004 VNF/PNF package onboarding, and stores the original vendor VNF/PNF package inside the SDC package – Ericsson contribution in Dublin
   1. PNF onboarding was tested
   2. VNF onboarding is being tested in El Alto / Frankfurt
2. SDC supports VNF/PNF package onboarding and/or accepts VNF/PNF package management interfaces from OSS/BSS via SOL005 Package Management APIs (TBD)
3. ONAP Runtime components store SOL004 Packages as needed
   1. For the SO case, SO stores SOL004 packages for NS, VNF and PNF by leveraging the ETSI Catalog DB microservices
4. SOL003 VNFM Adapter provides VNFMs Query/Fetch VNF packages/contents/artifacts, Reading VNFD and subscription/notification services
5. SOL005 Adapter provides NSD/PNFD management and SOL005 VNF package management

• Note: 

1. SOL007 (NS package) support is under discussion.
2. To simplify the package distribution and storage, the Runtime Catalog Manager is suggested for the future.

• ETSI Package Distribution Flows

Package Security

A VNF package uses the signature and certificate to ensure package integrity and validity. A CSAR file is digitally signed with the VNF provider private key. During the VNF package onboarding to SDC, SDC validates the package and then does the following:

• Transform SOL001-based VNFD into SDC internal models
• Store the original Vendor package into the ONBOARDING_PACKAGE directory