Page History

• SOL004 VNF/PNF Package includes SOL001 VNFD/PNFD with the original vendor package will be onboarded into SDC and  distributed from SDC to SVNFM/External NFVO.
• SOL007 NS Package includes SOL001 NSD with the original vendor package will be onboarded into SDC and distributed from SDC to SVNFM/External NFVO.
• SDC supports design of ETSI SOL007 compliant NSD packages and distribute them to SVNFM/External NFVO
• SDC supports Nested/Hierarchical ETSI SOL001 v2.7.1 NSD onboarding and distribution to ONAP runtime components.

• SOL003 and SOL005 Package Management APIs will be used for the distribution.
  • SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO

If the vendor package includes signature and certificate, ONAP supports the package security.

• 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
• SDC will store the vendor package with signature and certificate in a zip format in the ONBOARDED_PACKAGE directory.
• SO stores ONBOARDED_PACKAGE zip files in the ONAP-ETSI Catalog DB through ONAP-ETSI Catalog Manager APIs.
• SVNFM/NFVO extracts the CSAR file from the vendor package 
  • For Frankfurt, extracting the CSAR without validation is allowed

• VNF SDK will support SOL004 VNF package pre-onboarding for validation - optional
• VNF SDK will support SOL007 NS package pre-onboarding for validation - optional

SDC supports onboarding of the SOL004 VNF package includes SOL001 VNFD

• VNFD onboarding is testing in El Alto, and its regression testing will be done

• SOL004 VNF package onboarding is tested in El Alto
  • Further testing is necessary in Frankfurt
  • Mapping from SOL001 VNFD to SDC internal TOSCA template
  • Mapping from SOL001 VNFD to SDC AID DM is under consideration

SDC supports onboarding of the SOL004 PNF package includes SOL001 PNFD

• PNFD onboarding is done and its regression testing will be done

• SOL004 PNF package onboarding is done in Dublin
  • Mapping from SOL001 PNFD to SDC AID DM is done

• SOL007 NS package onboarding will be supported
  • Mapping from SOL001 NSD to SDC internal TOSCA template needs to be done
  • Mapping from SOL001 NSD to SDC AID DM is under consideration

SDC VSP and Resource CSAR files include the original vendor package

• This is done in Dublin and its regression testing will be done

• Storing the original vendor package in the SDC CSAR is done

The vendor package will be distributed from SDC to SVNFM/External NFVO

• The vendor package will be stored at the ONAP-ETSI Catalog DB
• SOL003 and SOL005 Package Management APIs will be used for the distribution
• SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO

• Refer to the ONAP-ETSI Catalog Manager, SO ETSI Catalog Manager and SOL003/SOL005 Package Management use cases

• ONAP supports vendor ETSI Package Security and validation

  • If the vendor package includes signature and certificate, ONAP supports the package security

• SOL004 VNF/PNF Package security will be supported by SDC, based on the package signature and certificate

• ONAP SDC supports the package security

• SOL007 NS Package security will be supported by SDC, based on the package signature and certificate

• ONAP SDC supports the package security

• SDC will store the vendor package with signature and certificate in a zip format in the ONBOARDED_PACKAGE directory.

• It is done in El Alto

• SO stores ONBOARDED_PACKAGE zip files in the ONAP-ETSI Catalog DB through ONAP-ETSI Catalog Manager APIs.

• Refer to the ONAP-ETSI Catalog Manager and SO ETSI Catalog Manager use cases

• SVNFM/NFVO extracts the CSAR file from the vendor package 
  • For Frankfurt, extracting the CSAR without validation is allowed

• SVNFM and External NFVO requirements on how to handle the zip-format packages
  • For Frankfurt, extracting the CSAR file without validation is allowed