...
- ETSI Package Onboarding and Distribution
- SOL004 VNF/PNF Package includes SOL001 VNFD/PNFD with the original vendor package will be distributed from SDC to SVNFM/External NFVO.
- SOL007 NS Package includes SOL001 NSD with the original vendor package will be distributed from SDC to External NFVO.
- SOL003 and SOL005 Package Management APIs will be used for the distribution.
- SOL004 VNF/PNF Package Security will be supported by the package signature and certificate.
- SOL007 NS Package Security will be supported by the package signature and certificate
- ETSI Package Pre-onboarding validation
- VNF SDK will support SOL004 VNF package pre-onboarding
- VNF SDK will support SOL007 NS package pre-onboarding
Feature Descriptions
Feature | Description |
---|---|
ETSI Package Management |
|
ETSI Package Security | If the vendor package includes signature and certificate, ONAP supports the package security.
|
ETSI Package Validation |
|
Epic and User Story
Epic | User Story | Description | Frankfurt? | JIRA | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Support ETSI Package Management ONAP supports ETSI package management ( onboarding and distribution)ONAP | SDC supports ETSI package management (onboarding and distribution) | Yes | and package security | Partially Done |
| ||||||||||||
SDC supports onboarding of the SOL004 VNF /PNF Packagepackage includes SOL001 VNFD /PNFD
|
| No |
| ||||||||||||||
SDC supports onboarding of the SOL004 PNF package includes SOL001 PNFD
|
| Yes | Done | ||||||||||||||
SDC supports onboarding of the SOL007 NS Package including package includes SOL001 NS |
| No |
| ||||||||||||||
SDC VSP and Resource CSAR files includesinclude the original vendor package
|
| Yes | Yes | Done | |||||||||||||
OSS/BSS onboards the vendor SOL007 NS package to SO directly through SOL005 Package Management APIs |
| TBD | The vendor package will be distributed from SDC to SVNFM/External NFVO
|
| Yes | - | |||||||||||
Support ETSI Package Security and validation |
| Yes |
| SDC already supports this in Dublin - Done
| |||||||||||||
|
| Done | - | ||||||||||||||
|
| No |
| ||||||||||||||
|
| Done | - | ||||||||||||||
|
| Yes | - | ||||||||||||||
|
| Yes | - | ||||||||||||||
Support of ETSI Package Validation | VNF SDK will support ETSI package validation for VNF and NS | TBD | |||||||||||||||
VNF SDK will support ETSI VNF package pre-onboarding for validation | VNF SDK will support ETSI VNF package pre-onboarding for validation | TBD | |||||||||||||||
VNF SDK will support ETSI NS package pre-onboarding for validation | VNF SDK will support ETSI NS package pre-onboarding for validation | TBD |
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
- SOL004 package includes SOL001 VNFD/PNFD
- PNF onboarding has been tested
- VNF onboarding will be tested in El Alto / Frankfurt
- SDC will support SOL007 NS package onboarding and store the original vendor NS package inside the SDC package
- NS onboarding will be supported
- This feature is postponed to the Guilin release
- SDC supports VNF/PNF package management interfaces from OSS/BSS via SOL005 Package Management APIs (TBD)
- SO supports NS package management interfaces from OSS via SOL005 Package Management APIs (TBD)
- ONAP Runtime components store SOL004 Packages for their operations
- For the SO case, SO stores SOL004 packages for VNF and PNF by leveraging the ONAP-ETSI Catalog Manager
- For the SO case, SO stores SOL007 packages for NS by leveraging the ONAP-ETSI Catalog Manager
- SOL003 VNFM Adapter provides VNFMs Query/Fetch VNF packages/contents/artifacts, Reading VNFD and subscription/notification services
- SOL005 Adapter provides NS/PNF/VNF package management to VF-C/External NFVO by leveraging SOL005 package management APIs
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
- ETSI Package Distribution Flows
PlantUML Macro | ||
---|---|---|
| ||
@startuml participant OSS_BSS participant SDC participant SO participant ONAP_ETSI_Catalog_Mgr participant SOL003_Adapter participant SOL005_Adapter participant VNFM participant VFC participant Ext_NFVO autonumber OSS_BSS -> SDC : Vendor SOL004/SOL007 package onboarding,\nincluding SOL001 VNFD group VNF PACKAGE TO SVNFM SDC -> SO : ONAP internal package with the \noriginal vendor CSAR/Zip SO -> ONAP_ETSI_Catalog_Mgr: store ONAP internal package \nwith the original vendor CSAR/Zipinvoke ETSI Catalog Manager, passing ONAP_ETSI_Catalog_Mgr -> SDC : query the SDC CSAR with the SDC CSAR id ONAP_ETSI_Catalog_Mgr --> ONAP_ETSI_Catalog_Mgr : extract SOL004 package CSAR/Zip from the SDC CSAR \nand store it ONAP_ETSI_Catalog_Mgr -> SOL003_Adapter : retrieve the original vendor CSAR/Zip SOL003_Adapter -> VNFM : forward the original vendor CSAR/Zip end group VNF PACKAGE TO Ext NFVO SDC -> SO : ONAP internal package with the original vendor CSAR/Zip SO -> ONAP_ETSI_Catalog_Mgr : store ONAP internal package with the original vendor CSAR/Zip ONAP_ETSI_Catalog_Mgr -> SDC : query the SDC CSAR with the SDC CSAR id ONAP_ETSI_Catalog_Mgr --> ONAP_ETSI_Catalog_Mgr : extract SOL007 package CSAR/Zip from the SDC CSAR \and store it ONAP_ETSI_Catalog_Mgr -> SOL005_Adapter : retrieve the original vendor CSAR/Zip SOL005_Adapter -> Ext_NFVO : forward the original vendor CSAR/Zip end group VNF PACKAGE TO VFC SDC -> VFC : ONAP internal package with the original vendor CSAR/Zip end @enduml |
...
- Enhancement (Ericsson contribution) was made to the SDC Dublin to support SOL004 PNF onboarding with .zip and .csar file extensions.
- The enhancement can be used for VNF onboarding – it is being tested.
- SDC VSP and Resource csar files have the ONBOARDINGONBOARDED_PACKAGE, which contains the original vendor VNF package.
- The VNFM and external NFVO use the original vendor VNF/NS packages.
- ONAP-ETSI Catalog Manager will be changed for the location of the original vendor package.
...
- At onboarding, SDC checks the file extension and performs the following procedures
- If the file is .zip, SDC unzips
- If it has .cert & .cms, it is a package with security and security validation will be performed.
- If it does not include .cert & .cms, it is an existing Heat template onboarding, and SDC follows the Heat template onboarding procedure
- If the file is .zip, SDC unzips
- If the file is .csar, it is a package without security.
- Next, SDC will check the TOSCA.meta file.
- If it contains SOL004v2.?.1 keywords, the package will be handled as SOL004v2.?.1.
- Otherwise, it will be handled as existing TOSCA (non-SOL004) package onboarding which will not have the ONBOARDINGONBOARDED_PACKAGE artifact.
SDC SOL004/SOL007 VNF Package Security
...
- Transform SOL001-based VNFD into SDC internal models
- Store the original Vendor package into the ONBOARDINGONBOARDED_PACKAGE directory
- If the original vendor package is a zip file with signature and certificate, the ONBOARDINGONBOARDED_PACKAGE directory will contain the zip file.
- VNFM and VF-C will receive the zip-format file.
- For Frankfurt, the SVNFM and external NFVO will receive a zip-format package with signature and certificate if the original vendor package contains signature and certificate.
- SVNFM and NFVO will unzip the incoming zip package files and extract CSAR files from the zip package files without validation.
- After the Frankfurt release, it is assumed that SVNFM and NFVO validate the incoming packages based on signature and certificate.
...