Page History

...

• ETSI Package Onboarding and Distribution
  • SOL004 VNF/PNF /NS 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 SVNFM/ 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

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 /NS package inside the SDC package
   1. SOL004 package includes SOL001 VNFD/NSD/PNFD TOSCA service template
   2. PNF onboarding was has been tested
   3. VNF onboarding is being will be tested in El Alto / Frankfurt
2. SDC will support SOL007 NS package onboarding and store the original vendor NS package inside the SDC package
   1. NS onboarding will be supported in Frankfurt
   2. This feature is postponed to the Guilin release
3. SDC supports VNF/PNF package onboarding and/or accepts VNF/PNF management interfaces from OSS/BSS via SOL005 Package Management APIs (TBD)
4. SO supports NS package management interfaces from OSS /BSS via SOL005 Package Management APIs (TBD)
5. ONAP Runtime components store SOL004 Packages as neededfor their operations
   1. For the SO case, SO stores SOL004 packages for NS, VNF and PNF by leveraging the ONAP-ETSI Catalog Manager
   2. For the SO case, SO stores SOL007 packages for NS by leveraging the ONAP-ETSI Catalog DB microservicesManager
6. SOL003 VNFM Adapter provides VNFMs Query/Fetch VNF packages/contents/artifacts, Reading VNFD and subscription/notification services
7. 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.

1. NS/PNF/VNF package management to VF-C/External NFVO by leveraging SOL005 package management APIs

• ETSI Package Distribution Flows

@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.

...

1. At onboarding, SDC checks the file extension and performs the following procedures
   1. If the file is .zip, SDC unzips
      1. If it has .cert & .cms, it is a package with security and security validation will be performed.
      2. If it does not include .cert & .cms, it is an existing Heat template onboarding, and SDC follows the Heat template onboarding procedure
2. If the file is .csar, it is a package without security.
3. Next, SDC will check the TOSCA.meta file.
4. If it contains SOL004v2.?.1 keywords, the package will be handled as SOL004v2.?.1.
5. 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

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.

SDC validates the VNF packages based on the embedded signature and certificate by leveraging CA.

• 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

...

• 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.

...