ETSI Package Management

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Ā 

Feature Descriptions

Feature

Description

Feature

Description

ETSI Package Management

  • 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 SVNFM/External NFVO.

  • SOL003 and SOL005 Package Management APIs will be used for the distribution.

    • SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO

ETSI Package Security

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

ETSI Package Validation

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

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

Epic and User Story

Epic

User Story

Description

Frankfurt?

JIRA

Epic

User Story

Description

Frankfurt?

JIRA

Support ETSI Package Management onboarding and distribution



SDC supports ETSI package management (onboarding and distribution) and package security

Partially Done

SDC-2610: Support Onboard ETSI 3.3.1 SOL004 compliant VNF / CNF packagesClosed



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

No

SDC-2611: Support for onboarding ETSI v3.3.1 SOL001 VNF DescriptorsClosed



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

Yes

Done



SDC supports onboarding of the SOL007 NS package includes SOL001 NS

  • 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

No

SDC-2612: SDC supports onboarding of the SOL007 NS package for VFC as the NFVOClosed



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

Yes

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

Yes

-



Support ETSI Package Security and validation

  • ONAP supports vendor ETSI Package Security and validation

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

Yes

SDC-2613: SDC supports ETSI 3.3.1 Package security and validation for SOL007 and SOL004 packagesClosed



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

  • ONAP SDC supports the package security

Done

-



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

  • ONAP SDC supports the package security

No

SDC-2614: SDC supports SOL007 NS Package securityClosed



  • 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

Done

-



  • 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

Yes

-



  • SVNFM/NFVO extracts the CSAR file from the vendor packageĀ 

    • For Frankfurt, extracting the CSAR without validation is allowed