...
The following assumptions are made before following the steps of this wiki:
- All components are deployed in an OpenStack environment.
- ONAP (Beijing release) has already been deployed on a Kubernetes cluster with the required components listed below.
- You can successfully access the Kubernetes cluster where ONAP is deployed at using the kubectl CLI.
- While Rancher is the Kubernetes-based container management platform of choice for testing the steps below, it is not required and other Kubernetes orchestrators can be used (i.e. Cloudify)
...
- vFW-vSINK preload file to use in SDNC’s ODL: https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/101589116220232/vfw_preload_beijing.txt?version=1&modificationDate=1537300585000&api=v2
- vPacketGen preload file to use in SDNC’s ODL: https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/101589116220232/vpacketgen_preload_beijing.txt?version=1&modificationDate=1537300585000&api=v2
- vFW-vSINK HEAT template template (Beijing – stable release) to use as part of uploading it into Portal’s SDC’s Widget. These 3 files will have to be put in a single zip file in a later step:
- HEAT template (Beijing – stable release): https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/vFWCL/vFWSNK/base_vfw.yaml;h=fe7f8dc64bfc7fb289318de74e6b8dce49d485c0;hb=refs/heads/beijing
- ENV file (Beijing – stable release): https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/vFWCL/vFWSNK/base_vfw.env;h=a6c4c73862592f262ba2e533ea0a4e4f9786d5e2;hb=refs/heads/beijing
- vPacketgen HEAT template (Beijing – stable release) to use as part of uploading it into Portal’s SDC’s Widget. These 3 files will have to be put in a single zip file in a later step:
- HEAT template (Beijing – stable release): https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/vFWCL/vPKG/base_vpkg.yaml;h=160331bf807b95d6f86b20118a15b26abfeb7153;hb=refs/heads/beijing
- ENV template (Beijing – stable release): https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/vFWCL/vPKG/base_vpkg.env;h=317fde9eedda848598061ca5f07580ac0b6edf91;hb=refs/heads/beijing
- MANIFEST File: https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/vFWCL/vPKG/MANIFEST.json;h=482b429474e4fbed180524793747a6d424169fea;hb=refs/heads/beijing
- File to mount the VNF in APPC’s ODL: https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/1600937116257085/appc_mountpoint.txt?version=1&modificationDate=1511893778000&api=v2
Prepare the HEAT Packages
...
Once the values that need to be filled out above, create two zip files containing the two HEAT packages we need to upload to the Portal SDC Widget in later steps.
Accessing the Portal GUI on your local browser (Kubernetes-based approach)
In order to setup your local machine to access the Portal Web GUI and continue with the steps of this documentation, please follow the instructions in Accessing ONAP Portal using OOM and a Kubernetes Cluster.
You should now be able to successfully view the Portal GUI Login page at http:
...
| language | bash |
|---|---|
| theme | Eclipse |
| linenumbers | true |
...
//portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm.
NOTE: It is recommended to access the Portal GUI through your browser's cookie-disabled window. In chrome, go on Incognito window with Ctrl + Shift + N. In Firefox, go on a Private window with Ctrl + Shift + P.
ONAP Portal Users and their Roles
As part of this demo, we will have to login to a number of different Portal user accounts in order to execute the appropriate flow to ultimately deploy the vFirewall VNFs into your OpenStack environment (NOTE: default password for all user accounts below is demo123456!)
Username | Role | Description |
|---|---|---|
| cs0008 | DESIGNER | Takes care of creating all the SDC resources, uploading the HEAT template, distributing the VNFs, etc.) |
| demo | SUPERUSER | This is the Administrator account that has access to actions that require admin rights. This is the user that will trigger the action to ultimately deploy the VF Module (actual VNF HEAT Template execution). |
| gv0001 | GOVERNOR | |
| jm0007 | TESTER | Takes care of running the tests for the VNF, and approving that tests were successful. |
| op0001 | OPERATOR |
Creating the Vendor License Model
In this part, we will create a Vendor License Model that will be tied to the Virtual Service Product (VSP) representing the vFirewall VNF package.
In a production VNF, every VNF vendor has a license mechanism that authorizes the use of the VNF in an environment. This includes license details and agreements that are between between this VNF vendor and the Service Provider that will ultimately deploy the VNF.
In this demo, we will create a VLM since it is a requirement to successfully onboard the VSP in your environment. The following are some details around the VLM, which will be executed in one way or another in later steps:
- The vendor details have to always be provided as part of the VLM definitions, and such vendor only needs to be specified once.
- In order to have a valid and functional VSP, a VLM needs to be mapped to it.
- A single VLM can have multiple license agreements mapped to it.
- VLM components that will need to be created are:
- License Agreements:
- Entitlement Pools:
- Feature Groups:
- License Key Groups: