The following diagram depicts a possible 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/PNA package management interfaces from OSS/BSS via SOL005 Package Management APIs.
- For now, the onboarding case is the focus
- ONAP Runtime components store SOL004 packages as needed.
- For the SO case, see the SO ETSI Catalog DB support for NS, VNF and PNF
- SOL003 VNFM Adapter provides VNFMs Query 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
- Location of SOL003 and SOL005 Adapters are under discussion and where/how the adapters get packages is under discussion
- SOL003 Adapter will continue to be part of SO and the adapter will expose its NBI to any client.
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