Page Comparison

...

Exec into any pod within your ONAP deployment that is connected to the primary ONAP network, this . This will give you access to using the internal service hostnames.
(Please note, for the following sets of CURLs this guide will be making use of the VNFM Simulator, you will need to edit the CURLs to match your specific VNFM's requirements, if they differ)

Step 2:

Send the following CURL to add the AAI Cloud Infrastructure ESR System Info List Entry, ensuring . Ensuring you alter the values to match your deployment's AAI Data:

curl -X PUT -H 'Accept: application/json' -H 'Authorization: Basic YWFpQGFhaS5vbmFwLm9yZzpkZW1vMTIzNDU2IQ==' -H 'Content-Type: application/json' -H 'X-FromAppId:12' -H 'X-TransactionId: 12' https://aai.onap:8443/aai/v15/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/regionOne/esr-system-info-list/esr-system-info/vnfmSimulator -d '{"name": "vnfmSimulatorName", "system-type": "simulator", "vimId": "myCloud", "vendor": "EST", "version": "V1.0", "certificateUrl": "", "url": "http://so-vnfm-simulator.onap:9093/vnflcm/v1/", "user-name": "vnfm", "password": "password1$"}' -k

Step 3:

Next you will need to send the following 2 CURLs in order to add entries into the AAI External System ESR VNFM List:

curl -X PUT -H 'Accept: application/json' -H 'Authorization: Basic YWFpQGFhaS5vbmFwLm9yZzpkZW1vMTIzNDU2IQ==' -H 'Content-Type: application/json' -H 'X-FromAppId:12' -H 'X-TransactionId: 12' https://aai.onap:8443/aai/v15/external-system/esr-vnfm-list/esr-vnfm/vnfmSimulator -d '{"vnfmId": "vnfmSimulator", "name": "vnfmSimulatorName", "type": "simulator", "vendor":

...

 "est"}'

curl -X PUT -H 'Accept: application/json' -H 'Authorization: Basic YWFpQGFhaS5vbmFwLm9yZzpkZW1vMTIzNDU2IQ==' -H 'Content-Type: application/json' -H 'X-FromAppId:12' -H 'X-TransactionId: 12' https://aai.onap:8443/aai/v15/external-system/esr-vnfm-list/esr-vnfm/vnfmSimulator/esr-system-info-list/esr-system-info/vnfmSimulatorId -d '{"esr-system-info-id": "vnfmSimulatorId", "type": "simulator", "user-name": "vnfm", "password": "password1$", "system-type": "simulator", "service-url": "http://so-vnfm-simulator.onap:9093/vnflcm/v1"}'

...

Step 4:

Take note of the "system-type" and "type" values you have added with these CURLs, as this . This will be used at a later stage when creating your VF in SDC.

Onboard a VNF package along with a Network Service CSAR into SDC.

This section of this guide can be seen in video format at the following link: https://wiki.onap.org/display/DW/SO+NFVO+NS+Onboarding+and+LCM+A video demonstration of this process "Onboarding ETSI Based NS" can be found here: SO NFVO NS Onboarding and LCM Demonstrations
It is recommended that you view the "Onboarding ETSI Based NS" this video before/alongside this section of the guide.

...

Login to the ONAP Portal. (Link: https://portal.api.simpledemo.onap.org:30225/ONAPPORTAL/login.htm (where "msbportal.api.simpledemo.onap.org" is set as the IP of your VM/host of your Portal component.)

...

1: Click the “ONBOARD” tab near the top of the window.
2: Create a “VLM” if you have not created a "VLM" before.
- From the “ONBOARD” page, click create VLM.
- Enter name and description, then select create.
- Click on the plus button beside Entitlement Pool.
- Add Name and Manufacturing Reference Number, then click save.
- Click on the plus button beside License Key Groups.
- Add Name and select type, then click save.
- Click on the plus button beside Feature Groups.
- In the general tab, add name, Description and Part Number. Move to the Entitlements Pools tab, select the entitlement pool you just created and click the rightward arrow. Move to the License Key Group tab, select the license key group you just created and click the rightward arrow. Once these three things are done, click save.
- Click on the plus button beside License Agreement.
- Add Name and select License Term. Next move to the Feature Groups tab, select the Feature Group you just created and click the rightward arrow. Lastly click save.
- On the overview page, select submit in the top right corner of the screen.
- Enter a commit comment and click Commit & Submit.

3: Next you will need to Create a Virtual Service Product (VSP)
- Click the “ONBOARD” tab near the top of the window.
- Click “CREATE NEW VSP” and fill in the required information. Make sure to select “Network Package” for the “ONBOARDING PROCEDURE” section. Then click “CREATE”.
- Now you will need to click Click where it says shows “! Missing” underneath “License Agreement”. Simply select a “Licensing Version” and “License Agreement/Feature Group” from the drop downs.
- Next click Click the “Overview” tab on the left hand side. Then press “Select File” in the “SOFTWARE PRODUCT ATTACHMENTS” section and select your prepared VNF Package. If you are onboarding a supported zip, then click “PROCEED TO VALIDATION” once you can see your added files. You can safely ignore any warnings that come up at this step, but not any errors. (Note: The package validation does not support CSARs currently, they will still work however, providing they meet SDC requirements.)

...

1: In the “HOME” tab of the SDC ONAP Portal, hover over the “ADD” square and select “ADD SERVICE”. Fill in the required fields, select the "Category" "Network Service" and press “Create” in the top right-hand corner.

2: Now you You will be brought to the draft page of your Service. Go to the “Composition” tab on the left-hand side and drag/drop the VF, that you just created, into this service (you can search for the VF by name in the top left).

...

It is recommended that you view the "ETSI Based NS Orchestration Demo" video before/alongside this section of the guide.

Create NS

Step 1:

First you will need to retrieve the NSD ID from the ETSI Catalog Database in order to populate the Create Network Service CURL. The ETSI Catalog Database will be found within the Modeling DB container.

Once logged Log into the ETSI Catalog Database and retrieve the data from the "catalog_nspackage" table, the . The value under the column "NSPACKAGEID" will be the NSD ID required as part of the Create Network Service CURL.

Step 2:

Next you will need to Exec into any pod within your ONAP deployment that is connected to the primary ONAP network, this . This will give you access to using the internal service hostnames.

...

Send the following Create Network Service CURL Command, ensuring your deployment's Global Customer ID (from AAI) and your NSDID (from ETSI Catalog Database) replace the values within the <>:

curl -k -X POST http://so-etsi-nfvo-ns-lcm.onap:9095/so/so-etsi-nfvo-ns-lcm/v1/api/nslcm/v1/ns_instances -H "Authorization: Basic c28tZXRzaS1uZnZvLW5zLWxjbTpEdXJnMSREYWxhWG95ZA==" -H "accept:application/json" -H "Content-Type:application/json" -H "HTTP_GLOBALCUSTOMERID: <GLOBALCUSTOMERID>" -d '{"nsdId": "<NSDID>", "nsName": "demo", "nsDescription": "demo"}' -v

You should receive a synchronous response back almost immediately. This response will contain the NS Instance ID of the NS Instance we just created, take note of this as it will be needed in the following steps.

After this step has been completed you should be able to log into the Marie-Db-Galera-0 Pod on your ONAP deployment, then connect to the "NFVO" database, and retrieve . Retrieving all data from the "ns_inst" table . This will show that your initial NS has been created.

Instantiate NS

Step

...

1:

Next you will need to create a JSON file on the pod, which you are exec'ed into, named "Payload.json" in the following example.

...

{

...

    "nsFlavourId": "default",

...

    "locationConstraints": [{

...

        "vnfProfileId": "b1bb0ce7-2222-4fa7-95ed-4840d70a1177"

...

    }],

...

    "additionalParamsForVnf":

...

 [{
        "vnfProfileId": "b1bb0ce7-2222-4fa7-95ed-4840d70a1177",

...

        "vnfInstanceName": "vgwVnf1",

...

        "vnfInstanceDescription": "test",

...

        "additionalParams":

...

 {
            "vim_id": "<cloud-owner>_<cloud-region-id>_<tenant_id>"

...

}

}]

        }
    }]
}

In the above Payload.json, you must ensure that the "vnfProfileId" matches the VNF Descriptor ID found in the VNF CSAR which you onboarded as part of the VNF Onboarding section of this guide. The "vnfInstanceName" must match your VNF's name, and finally the "vim_id" must be replaced with your AAI Data values for your deployment's Cloud-Owner, Cloud-Region-Id and Tenant-Id respectively.

Step

...

2:

Next you will need to send the following CURL command in order to trigger the instantiation of the Network Service. Ensure that you add the NS Instance ID received in the Create NS response to the URL Path (replacing <NS_INSTANCE_ID>), and match the Global Customer ID as before:

curl -k -X POST http://so-etsi-nfvo-ns-lcm.onap:9095/so/so-etsi-nfvo-ns-lcm/v1/api/nslcm/v1/ns_instances/<NS_INSTANCE_ID>/instantiate -H "Authorization: Basic c28tZXRzaS1uZnZvLW5zLWxjbTpEdXJnMSREYWxhWG95ZA==" -H "accept: application/json" -H "Content-Type:application/json" -H "HTTP_GLOBALCUSTOMERID: ADemoCustomerInXcloud" -d @Payload.json -v

This will trigger the Asynchronous Instantiate NS Functionality. You will receive a response confirming that the process has begun , you with a 201 HTTP Response Header. You can view the debug.log files on the following pods in order to view the progress:

• SO-ETSI-NFVO-NS-LCM
• SO-ETSI-VNFMSOL003-ADAPTER
• SO-VNFM-SIMULATOR (If making use of the VNFM-Simulator, alternatively the logs of the VNFM you are using)

Once the full instantiation has been completed, reconnect to the "NFVO" database, within the Marie-Db-Galera-0 pod on your ONAP deployment. Retrieving all data from the "ns_inst" table again, you should see that the "STATUS" field for your NS has changed to "InstantiatedINSTANTIATED".

Terminate NS

Step

...

1:

Send the following CURL command in order to trigger the Termination of the Network Service. Ensure that you add the NS Instance ID received in the Create NS response to the URL Path (replacing <NS_INSTANCE_ID>), and match the Global Customer ID as before:curl -k -X POST :

curl -k -X POST http://so-etsi-nfvo-ns-lcm.onap:9095/so/so-etsi-nfvo-ns-lcm/v1/api/nslcm/v1/ns_instances/<NS_INSTANCE_ID>/terminate -H "Authorization: Basic c28tZXRzaS1uZnZvLW5zLWxjbTpEdXJnMSREYWxhWG95ZA==" -H "accept: application/json" -H "Content-Type: application/json" -v

Similar to the Instantiate functionality, this is an asynchronous call and as such , so you will receive a response to your CURL commandconfirming that the process has begun with a 201 HTTP Response Header. As above, view the specified debug.log files in order to view the progress.

Once the full termination has been completed, reconnect to the "NFVO" database, within the Marie-Db-Galera-0 pod on your ONAP deployment. Retrieving all data from the "ns_inst" table again, you should see that the "STATUS" field for your NS has changed back to "CreatedNOT_INSTANTIATED".

Delete NS

Step

...

1:

Finally you will need to send send the following CURL command in order to trigger the Deletion of the Network Service. Ensure that you add the NS Instance ID received in the Create NS response to the URL Path (replacing <NS_INSTANCE_ID>), and match the Global Customer ID as before:curl -k -X DELETE :

curl -k -X DELETE http://so-etsi-nfvo-ns-lcm.onap:9095/so/so-etsi-nfvo-ns-lcm/v1/api/nslcm/v1/ns_instances/<NS_INSTANCE_ID> -H "Authorization: Basic c28tZXRzaS1uZnZvLW5zLWxjbTpEdXJnMSREYWxhWG95ZA==" -H "accept: application/json" -H "Content-Type: application/json" -v

Similar to the Create functionality, this is an a synchronous call and as such you will receive the actual job response to your CURL command.

Once the full deletion has been completed, reconnect to the "NFVO" database, within the Marie-Db-Galera-0 pod on your ONAP deployment. Retrieving all data from the "ns_inst" table again, you should no longer be able to see that the NS Instance has now been deletedin the NS_INST table.

<DRAFT> Further Content Coming Below

...