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
Feature | Description |
|---|---|
| ETSI Package Management | Package Management of SOL004 including SOL001, based on SOL005 and SOL003 Package Management APIs
|
Epic and User Story
Epic | User Story | Description |
|---|---|---|
| ETSI Package Management | Package Management of SOL004 including SOL001, based on SOL005 and SOL003 Package Management APIs
| |
ETSI Package Management Architecture
The diagram depicts the package management architecture.
- SDC supports SOL004 VNF/PNF package onboarding, and stores the original vendor VNF/PNF package inside the SDC package – Ericsson contribution in Dublin
- PNF onboarding was tested
- VNF onboarding is being tested in El Alto / Frankfurt
- SDC supports VNF/PNF package onboarding and/or accepts VNF/PNF package management interfaces from OSS/BSS via SOL005 Package Management APIs (TBD)
- ONAP Runtime components store SOL004 Packages as needed
- For the SO case, SO stores SOL004 packages for NS, VNF and PNF by leveraging the ETSI Catalog DB microservices
- SOL003 VNFM Adapter provides VNFMs Query/Fetch VNF packages/contents/artifacts, Reading VNFD and subscription/notification services
- SOL005 Adapter provides NSD/PNFD management and SOL005 VNF package management
- Note:
- SOL007 (NS package) support is under discussion.
- 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
- If the original vendor package is a zip file with signature and certificate, the ONBOARDING_PACKAGE directory will contain the zip file.
- VNFM and VF-C will receive the zip-format file. For Frankfurt release, VNFM and VF-C will unzip the file and take the CSAR file from the zip file without validation.