Pre-Onboarding

Generate Manifest and Package Artifacts

Note

This section describes the steps required to package a given HEAT template into a zip-file, which can be onboarded to SDC. Instructions to create TOSCA based VNF or PNF Onboarding Packages are not described here

The for onboarding the zip-file requires besides the Heat template also a MANIFEST.json file, which describes the content of the package. To generate a MANIFEST.json file a script can be used offered by the SDC project: generate-manifest.py

These steps are performed outside SDC.

Prerequisites: Obtain Heat/ENV files and other files required for onboarding. The requirements are found in the following document.

Heat requirements

  1. Put the Heat, ENV, nested Heat, and other files used by get-file in templates in a directory on a host, which supports python.

    Naming guidelines:

    • The base Heat should include “base” in the name.
    • The ENV file name should match the name of the Heat file with which it is associated.
    • All get-file file names need to be unique.
  2. Put the python script in a directory one level above the directory that contains the Heat/ENV and other files.

    For example, [dir x]/[dir y]

    • [dir y] contains the Heat/ENV files and other files
    • [dir x] contains the python script
  3. Run the script via command line:

    python generate-manifest.py -f "dir y"
    
  4. Examine the manifest file and confirm that is correct.

  5. Package all Heat/ENV files, all other files, and the MANIFEST.json into one .zip file.

Example packages can be found in the SDC poject: example-packages

Validate xNF Package (VNF/PNF)

VNF and PNF packages have to follow the requirements described in:

VNF and PNF Modeling Requirements

ONAP Management Requirements

For Validation of VNF and PNF packages the tools delivered by VNFSDK can be used:

Prior to resource onboarding, the Certification Group does the following:

  • for VNF and PNF
    • Validation of the delivered xNF package and artifacts
    • using the VNF Validation Tools
  • in case of VNF
    • onboards the Heat template(s) and metadata to the SDC catalog
    • creates a test VF
    • runs the Heat scanning tools
  • shares the results with any group that approves Virtual Functions

In parallel, the Certification Group onboards the VF Image and OS to a standalone ONAP instance (the “sandbox”) and performs the following:

  • security scan
  • compatibility test for the OS and vendor binary
  • malware scan

The Certification group then instantiates the VF image using the vendor Heat (if provided) in order to validate that the VM can run on the Network Cloud.

No VF functionality testing is performed at this stage.