Create a Tenant


This section is not really belonging to the “Design” phase, but to the preparation of the “Service Deployment” and will be moved in the next release

Each service requires a tenant (a group of users who share a common access) in which resources are stored in the cloud. This process is performed using facilities of the network cloud, outside of ONAP. Confirm that the tenant is created and note the tenant ID.

ONAP admin users can configure a cloud-owner to add new cloud resources. These are the computing and networking resources, that will support running VNFs. A cloud-owner holds a keystone URL, login, region and password, in the case of an Openstack cluster. A cloud-owner also belongs to a region. The region name should be the same as the Openstack region. Prior to creation of a cloud-owner, its region must be created first. Multiple tenants can share the same cloud-owner. Note that these tenants are ONAP tenants, not Openstack tenants. Tenant register services that customers are allowed to deploy. Finally, the customer is like an instance of the tenant.

Note: there is no GUI (yet) to configure these objects. REST requests are sent to AAI to achieve the configuration. For a detailed list of required REST commands see:

The overall process is as follows:

  1. Create a region and a cloud-owner. This steps registers Openstack credentials. This is the only step requiring entering Openstack specific parameters.
  2. Create a complex. The complex describes the coverage of the region with a street address etc.
  3. Create a service. The service name should match the name of the service onboarded in SDC.
  4. Create a tenant. Tenant in ONAP stores a design for a generic customer.
  5. Associate tenants with their allowed services.
  6. Create an instance of the tenant or customer. The customer is visible in VID. A VID user can deploy allowed services on this new customer.

Generate Manifest and Package Artifacts


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

Before onboarding resources, run to generate a MANIFEST file. 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.

    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 on the Windows command line (not valid anymore):

    python -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.

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.