VNFSDK Dublin Release (WIP)

The VNF package provided by a   VNF vendor **MAY** be either with TOSCA-Metadata directory (CSAR Option 1) or   without TOSCA-Metadata directory (CSAR Option 2) as specified in ETSI GS   NFV-SOL004. On-boarding entity (ONAP SDC) must support both options. 

**Note:** SDC supports only the CSAR Option   1 in Casablanca. The Option 2 will be considered in future ONAP releases, VNF MAY VNF Package Structure and Format

The VNF provider MUST enumerate all of the open source licenses their VNF(s) incorporate. CSAR License directory as per ETSI SOL004.

for example ROOT\Licenses\ License_term.txt

The VNF Descriptor (VNFD) provided by VNF vendor MUST comply with TOSCA/YAML based Service template for VNF descriptor specified in ETSI NFV-SOL001.

Note: As the ETSI NFV-SOL001 is work in progress the below tables summarizes the TOSCA definitions agreed to be part of current version of NFV profile and that VNFD MUST comply with in ONAP Release 2+ Requirements.

A VNFD is a deployment template which describes a VNF in terms of deployment and operational behavior requirements. It contains virtualized resources (nodes) requirements as well as connectivity and interfaces requirements and MUST comply with info elements specified in ETSI GS NFV-IFA 011. The main parts of the VNFD are the following:

• VNF topology: it is modeled in a cloud agnostic way using virtualized containers and their connectivity. Virtual Deployment Units (VDU) describe the capabilities of the virtualized containers, such as virtual CPU, RAM, disks; their connectivity is modeled with VDU Connection Point Descriptors (VduCpd), Virtual Link Descriptors (VnfVld) and VNF External Connection Point Descriptors (VnfExternalCpd);
• VNF deployment aspects: they are described in one or more deployment flavours, including configurable parameters, instantiation levels, placement constraints (affinity / antiaffinity), minimum and maximum VDU instance numbers. Horizontal scaling is modeled with scaling aspects and the respective scaling levels in the deployment flavours;

Note: The deployment aspects (deployment flavour etc.) are postponed for future ONAP releases.

• VNF lifecycle management (LCM) operations: describes the LCM operations supported per deployment flavour, and their input parameters; Note, thatthe actual LCM implementation resides in a different layer, namely referring to additional template artifacts.

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.

R-02454

The VNF Package MUST include all relevant playbooks to ONAP to be loaded on the Ansible Server.

Note: Only applicable if the VNF providers claim this product support Chef, Ansible.

The VNF Package MUST  include a cookbook to be loaded on the appropriate server if the VNF is managed via Chef.

Note: Only applicable if the VNF providers claim this product support Chef, Ansible.

The VNF Package MUST include all relevant Chef artifacts (roles/cookbooks/recipes) required to execute VNF actions requested by ONAP for loading on appropriate Chef Server.

Note: Only applicable if the VNF providers claim this product support Chef, Ansible.

The VNF MUST make available (or load on VNF Ansible Server) playbooks that conform to the ONAP requirement.

Note: Only applicable if the VNF providers claim this product support Chef, Ansible.

The VNF Package MUST include all relevant cookbooks to be loaded on the ONAP Chef Server.

Note: Only applicable if the VNF providers claim this product support Chef, Ansible.

(Test only) CERTIFICATE check. In the PNF package it is expected that there will be MainServiceTemplate.cert. This is mentioned in the TOSCA MetaFile. For example, in the TOSCA MetaFile, it could be mentioned "Entry-Certificate: Artifacts/resource-gnodeb-template.cert". And VNF SDK would check to make sure that the resource-gnodeb-template.cert file exists in the mentioned directory, the Artifacts in this case. VNF SDK does not look inside this file.

For details, consult chapter 5.2 of the ETSI NFV SOL 004 doc here: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/004/02.05.01_60/gs_nfv-sol004v020501p.pdf

(Needs Investigation) SOL004 has option 1 (signing each artifact individually / individual digest) and option 2 (sign entire package). It would be nice if VNF SDK supported both Option 1 and Option 2.

Driven from SOL004: Option 1 (Supported in R4 Dublin): TOSCA.meta (exists) Meta-directory based, XML based approach. Option 2 (NOT support in R4 Dublin): CSAR without TOSCA.meta. Manifest (.mf) file that has everything (so the TOSCA.meta is redundant). Yaml-based approach.

The Public Key a key to open the package. SOL004 Option 1, 2 and use key to open the package - X.509 certificates public key, private key to sign the package and private key correspond to the private key of the package also delivered with the package. a package, a signature, and public key certificate delivered together. There may be more than one signature. Option 1 there is a digest for every file. All of those digests are listed in the manifest file. The manifest file is signed, one signature on the manifest. One signature and one key/pair & 1 certificate. Still optional to sign other files. The signature is a file beside. myimage.iso myimage.xyz but the same file/directory. Every file signed should have a signature files. CSAR file signed in a .sm file, package signature. The public key is signed can be signed by a root certificate.

An X.509 certificate is a digital certificate that uses the widely accepted international X.509 public key infrastructure (PKI) standard to verify that a public key belongs to the user, computer or service identity contained within the certificate.

Level 1: Test VNF Package API is accessible or not

Level 2: Test VNF Package API 's response is correct or not

Level 1 is Compliance Test .

Level 2 could be validation Test.

Level 1: Test VNF instances API is accessible or not

Level 2: Test VNF instances API 's response is correct or not

Level 1: Test VNF Terminate API is accessible or not

Level 2: Test VNF Terminate API 's response is correct or not

Level 1: Test VNF Scale API is accessible or not

Level 2: Test VNF Scale API 's response is correct or not

Level 1: Test VNF Heal API is accessible or not

Level 2: Test VNF Heal API 's response is correct or not