...
VNF Package Structure and Format
R-XXXXXXXX: The VNF package MUST be arranged as a CSAR archive as specified in TOSCA Simple Profile in YAML 1.2.
O-XXXXXXXX: The VNF package provided by a VNF vendor MAY be either with TOSCA.meta directory (CSAR Option 1) or without TOSCA.meta directory (CSAR Option 2) as specified in ETSI GS NFV-SOL004. On-boarding entity (ONAP SDC) must support both options.
VNF Package Contents
R-XXXXXXXX: The VNF package MUST contain all standard artifacts as specified in ETSI GS NFV-SOL004 including Manifest file, VNFD (or Main TOSCA/YAML based Service Template) and other optional artifacts.
R-XXXXXXXX: The VNF package Manifest file MUST contain: VNF package meta-data, a list of all artifacts (both internal and external) entry’s including their respected URI’s, an algorithm to calculate a digest and a digest result calculated on the content of each artifacts, as specified in ETSI GS NFV-SOL004.
R-04298: The VNF provider MUST provide their testing scripts to support testing as specified in ETSI NFV-SOL004 - Testing directory in CSAR
R-26881: The VNF provider MUST provide the binaries and images needed to instantiate the VNF (VNF and VNFC images) either as:
- Local artifact in CSAR: ROOT\Artifacts\ VNF
...
- _Image.bin
- externally referred (by URI) artifact in Manifest file (also may be referred by VNF Descriptor)
Note: Currently , ONAP doesn't have the capability of Image management, we upload the image into VIM/VNFM manually.
VNF Package Authenticity
R-XXXXXXXX: The VNF package Manifest file MUST contain a Signature calculated on all the contents of the Manifest file, as specified in ETSI GS NFV-SOL004.
Note: Moved to Dublin release.
VNF Package ONAP Extensions
...