TOSCA VNF Onboarding With ONAP at 2020 ETSI NFV & MEC Plugtests


This blog describes onboarding of a TOSCA VNF with ONAP, an exercise that was conducted at the 2020 ETSI NFV & MEC Plugtests Event. This event was conducted online and the participants worked remotely.


The setup consisted of Aarna Networks ONAP Distribution (ANOD) 4.0 (based on the ONAP El Alto release). ONAP was hosted on bare metal servers and connected to WindRiver Openstack as the NFVI layer. Since the default components of ONAP had unresolved bugs in VFC related functionality, we upgraded a few of them to a higher version:

vfc-nslcm: nslcm:1.3.8

vfc-vnflcm: vnflcm:1.3.8

vfc-generic-vnfm-driver: vnfmgr:1.3.4


multicloud-windriver : 1.5.4

multicloud-framework: 1.5.1

The details of all the component versions for ONAP are here.

Next we upgraded the CLI to version 1.5.3. Then we followed the below steps.

1. We downloaded the VNF TOSCA CSAR package to be used. We used the following VNF:

2. Downloaded the LCM script from below location

3. Next we filled the Cloud details in “/opt/oclip/conf/vnf-tosca-lcm.json” file in anod-master:

   "cloud": {

       "identity-url": "",

       "username": "aarnanetworks-etsi",

       "password": "aarnanetworks@etsiPlugtest20",

       "region": "RegionOne",

       "version": "titanium_cloud",

       "tenant": "aarnanetworks-etsi"


4. Next we ran the “setup_cloud_and_subscription” section in file. This sets up the cloud information in ONAP.

5. We then uploaded the VNF csar and NS csar to UUI and then created and onboarded the VNF using UUI.

6. UUI can be accessed using the following URL. Here the IP address is that of anod-master

This concludes the steps required to onboard a TOSCA based ETSI compliant VNF onto ONAP.

We use cookies to enhance site navigation, analyze site usage, and assist in our marketing efforts. For more information, please see the Aarna Networks Cookie Policy.
Accept cookies