| Table of Contents |
|---|
Preparation
Install ONAP
Make sure that you've installed ONAP R1 (Amsterdam) release. For installation instructions, please refer ONAP Installation in Vanilla OpenStack.
...
| User | Role |
|---|---|
| demo | Operator |
| cs0008 | DESIGNER |
| jm0007 | TESTER |
| op0001 | OPS |
| gv0001 | GOVERNOR |
Create images for vBRG, vBNG, vGMUX, and vG
Follow the following instructions to build an image for each VNF and save them in your Openstack: ONAP vCPE VPP-based VNF Installation and Usage Information
To avoid unexpected mistakes, you may want to give each image a meaningful name and also be careful when mixing upper case and lower case characters. After this you should see images like below.
VNF Onboarding
Create License Model in SDC
Log in to SDC portal as designer. Create a license that will be used by the subsequent steps. The detailed steps are here: Creating a Licensing Model
Prepare HEAT Templates
vCPE uses five VNFs: Infra, vBRG, vBNG, vGMUX, and vG, which are described using five HEAT templates. For each HEAT template, you will need to fill the env file with appropriate parameters. The HEAT templates can be obtained from gerrit: [demo.git] / heat / vCPE /
...
For each VNF, compress the three env, yaml, and json files into a zip package, which will be used for onboarding. If you want to get the zip packages I used for reference, download them here: infra-sb01.zip, vbng-sb01.zip, vbrg-sb01.zip, vgmux-sb01.zip, vgw-sb01.zip.
VNF Onboarding in SDC
Onboard the VNFs in SDC one by one. The process is the same for all VNFs. Below is an example for onboarding infra.
...
In the search box, type in suffix of the vsp you onboarded a moment ago to easily locate the vsp. Then click 'Import VSP'.
Click 'Create' without changing anything.
Now a VF based on the HEAT is created successfully. Click 'Submit for Testing'.
Sign out and sign back in as tester: jm0007, select the VF you created a moment ago, test and accept it.