Use Cases
- 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
Requirements
The following requirements are defined in the Guilin release - functional requirements proposed list, Guilin release - functional requirements proposed list
- Onboard ETSI SOL004 compliant VNF packages
- Onboard ETSI SOL007 compliant Network Service Descriptor packages
- Design ETSI SOL007 compliant Network Service Descriptor packages
- Support for Nested/Hierarchical ETSI SOL001 v2.7.1 Network Service Descriptor
Feature Descriptions
Feature | Description |
---|---|
SDC ETSI Package Management |
|
SOL003/SOL005 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 | Guilin? | JIRA |
---|---|---|---|---|
Support ETSI Package Management onboarding and distribution | SDC supports ETSI package management (onboarding and distribution) and package security | Partially Done | ||
SDC supports onboarding of the SOL004 VNF package includes SOL001 VNFD
|
| No | ||
SDC supports onboarding of the SOL004 PNF package includes SOL001 PNFD
|
| Yes | Done | |
SDC supports onboarding of the SOL007 NS package includes SOL001 NS |
| No | ||
SDC VSP and Resource CSAR files include the original vendor package
|
| Yes | Done | |
The vendor package will be distributed from SDC to SVNFM/External NFVO
|
| Yes | - | |
Support ETSI Package Security and validation |
| Yes | ||
|
| 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.
...
PlantUML Macro | ||
---|---|---|
| ||
@startuml participant OSS_BSS participant SDC 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 SDC --> SDC : onboard SOL004/SOL007 package and put the vendor package\ninto the ONBOARD_PACKAGE directory ONAP_ETSI_Catalog_Mgr -> SDC : register for SDC notification SDC -> ONAP_ETSI_Catalog_Mgr : send a notification for SDC CSAR 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 SOL004/Sol007 package CSAR/Zip from the SDC CSAR \nand store it group VNF PACKAGE TO SVNFM ONAP_ETSI_Catalog_Mgr -> SOL003_Adapter : send a notification to SOL003_Adapter SOL003_Adapter -> VNFM : send a notification VNFM -> SOL003_Adapter : query for a VNF package SOL003_Adapter -> ONAP_ETSI_Catalog_Mgr : query for a VNF package ONAP_ETSI_Catalog_Mgr -> SOL003_Adapter : send a VNF package SOL003_Adapter -> VNFM : sends a VNF package end group VNF PACKAGE TO Ext NFVO ONAP_ETSI_Catalog_Mgr -> SOL005_Adapter : send a notification to SOL005_Adapter SOL005_Adapter -> Ext_NFVO : send a notification Ext_NFVO -> SOL005_Adapter : query for a VNF/PNF/NS package SOL005_Adapter -> ONAP_ETSI_Catalog_Mgr : query for a VNF/PNF/NS package ONAP_ETSI_Catalog_Mgr -> SOL005_Adapter : send a VNF/PNF/NS package SOL005_Adapter -> Ext_NFVO : sends a VNF/PNF/NS package end group VNF PACKAGE TO VFC ONAP_ETSI_Catalog_Mgr -> SOL005_Adapter : send a notification to SOL005_Adapter SOL005_Adapter -> VFC : send a notification VFC -> SOL005_Adapter : query for a VNF/PNF/NS package SOL005_Adapter -> ONAP_ETSI_Catalog_Mgr : query for a VNF/PNF/NS package ONAP_ETSI_Catalog_Mgr -> SOL005_Adapter : send a VNF/PNF/NS package SOL005_Adapter -> VFC : sends a VNF/PNF/NS package end @enduml |
SDC VNF/PNF Onboarding and Distribution
This section describes SDC VNF/PNF onboarding and the End-to-End package distribution from SDC to SVNFM/external NFVOs.
SDC takes the vendor provided package and adds some files or changes files and meta data according to SDC procedure.
SDC VNF/PNF Onboarding Procedure and Original Vendor VNF/PNF Package Handling
- 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 ONBOARDED_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 ONBOARDED_PACKAGE artifact.
SDC SOL004/SOL007 VNF Package Security
Among the SOL004/SOL007 VNF package security options, the SDC supports the option2 as depicted below. In the option 2, there are two ways to zip the VNF packages, and SDC supports both.
...
- Vendor SOL004/SOL007 VNF Package with certificate and signature is onboarded into SDC
- ZIP-format VNF package includes CSAR, Signature and Certificate
- SDC validates VNF package based on the certificate and signature
- SDC generates SDC internal model plus the vendor SOL004/SOL007 package CSAR and ZIP (with certificate and signature) – the supported format is TBD based on the security requirement
ETSI Package Distribution
ETSI packages will be distributed from SDC to other ONAP runtime components such as SO and VF-C. SO will store the packages to its ETSI Catalog DB and further distribute the packages to SVNFMs/external NFVOs thru the SOL003/SOL005 Adapters.
...