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