Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Feature

Description

ETSI Package Management
  • SOL004 VNF/PNF/NS Package includes SOL001 VNFD/PNFD/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.
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
  • SDC will store the vendor package with signature and certificate in a zip format in the ONBOARDING_PACKAGE directory.
  • SO stores ONBOARDING_PACKAGE zip files in the ONAP-ETSI Catalog DB through ONAP-ETSI Catalog Manager APIs.
  • SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO
  • SVNFM/NFVO extracts the CSAR files from the vendor packages 
    • For Frankfurt, without validation

Epic and User Story

Epic

User Story

Description

Support ETSI Package Management

ONAP supports ETSI package management (onboarding and distribution)

ONAP supports ETSI package management (onboarding and distribution)

SDC Supports ETSI package onboarding

  • SDC supports onboarding of the SOL004 VNF/PNF/NS Package includes SOL001 VNFD/PNFD/NSD TOSCA service
templates 
  • templates
    • PNFD onboarding is done
    • VNFD onboarding is tested in El Alto, and further testing is necessary
    • NSD onboarding is needed for SOL005 
  • SDC VSP and Resource CSAR files includes the original vendor package
    • This is done in Dublin
  • SOL004 PNF package onboarding is done in Dublin
  • Storing the original vendor package in the SDC CSAR is done
  • SOL004 VNF package onboarding is tested in El Alto
    • Further testing is necessary in Frankfurt
  • SOL004 NS package onboarding needs to be designed and implemented in Frankfurt

OSS/BSS onboards the vendor SOL004 NS package to SO directly through SOL005 Package Management APIs

The vendor package will be stored at the ONAP-ETSI Catalog DB

  • Verizon and Samsung are supposed to provide their use cases for this direct onboarding from OSS/BSS to SO. 
  • It is possible this onboarding path is out of scope from Frankfurt: TBD

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
Support ETSI Package Security

ONAP supports vendor ETSI Package Security

  • If the vendor package includes signature and certificate, ONAP supports the package security
  • ONAP SDC already supports this in Dublin - Done

SOL004 VNF/PNF Package security will be supported by the package signature and certificate

  • ONAP SDC supports this

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

  • It will be done in Frankfurt

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

SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO
  • Refer to the ONAP-ETSI Catalog Manager and SO ETSI Catalog Manager use cases

SVNFM/NFVO extracts the CSAR files from the vendor packages 

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

ETSI Package Management Architecture

...