Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
When a VIM/Cloud instance is used to deploy an ONAP instance, it will be registered to that ONAP instance by default. However, it is somehow tricky to add additional VIM/Cloud instance to ONAP instance with Amsterdam Release. This page is trying to share the practice to do so and the goal is to allow users deploy VNF/VF-Modules to the additional VIM/Cloud instance.
There are 3 places to store information of a VIM/Cloud instance: A&AI, SO, Robot. And it is very important to associate the VIM/Cloud instance with subscriber's service subscription, otherwise you will not able to deploy the subscriber's VNF/VF-Modules to that VIM/Cloud instance .
Prerequisite: Complex object and Subscribe object are created in the AAI
Complex object in A&AI represent the physical location of a VIM/Cloud instance, there are one-to-many association between them, so creating the complex object is out of scope of this practice. But I would like to share the POSTMAN script to do create complex named clli2 for your reference:
Subscriber registration and subscription to service is out of scope of this practice, a default subscriber "Demonstration" and service subscriptions are populated by Robot service.
Here are the commands to find out subscribers and their subscriptions.
open the portal by url: http://<multi-service VM IP>/iui/aai-esr-gui/extsys/vim/vimView.html
Click the "register button", the registration portal will show up.
Caveat: approach 2 which utilizes ESR VIM register portal will trigger MultiCloud to discover resources of VIM/Cloud instance and populate them into AAI. Right now with Amsterdam Release, it supports OpenStack ocata, Wind River Titanium Cloud, and VMware VIO. More options will be available in future releases.
Action 2: associate this cloud region object with a complex object
This association will be important for ONAP Beijing Release when OOF needs to find out the location approximity of different cloud regions.
SO does not utilize the cloud region representation in A&AI. It stores information of the VIM/Cloud instances inside of the container as configuration file. So to add a VIM/Cloud instance to SO, you need attach to the SO service container and then update the configuration file "/etc/mso/config.d/cloud_config.json" accordingly.
Below is the template for adding a new cloud site and the associate identity service.
ubuntu@vm0-so:~$ sudo docker exec -it testlab_mso_1 bash
root@mso:/# apt-get install vim
root@mso:/# vi /etc/mso/config.d/cloud_config.json
{
"cloud_config":
{
"identity_services":
{
"DEFAULT_KEYSTONE":
{
"identity_url": "http://10.12.25.2:5000/v2.0",
"mso_id": "demonstrable",
"mso_pass": "9f0933d3664e07961856781c9add38bc",
"admin_tenant": "service",
"member_role": "admin",
"tenant_metadata": true,
"identity_server_type": "KEYSTONE",
"identity_authentication_type": "USERNAME_PASSWORD"
},
"DEFAULT_KEYSTONE2":
{
"identity_url": "<keystone auth url, support only keystone API v2.0>",
"mso_id": "<username>",
"mso_pass": "<encrypted password by http://<MSO VM IP>:8080/networks/rest/cloud/encryptPassword/<password> >",
"admin_tenant": "service",
"member_role": "admin",
"tenant_metadata": true,
"identity_server_type": "KEYSTONE",
"identity_authentication_type": "USERNAME_PASSWORD"
}
},
"cloud_sites":
{
"RegionOne":
{
"region_id": "RegionOne",
"clli": "RegionOne",
"aic_version": "2.5",
"identity_service_id": "DEFAULT_KEYSTONE"
},
"<cloud_site name, must align to cloud-region-id in AAI>":
{
"region_id": "cloud_site name, must align to cloud-region-id in AAI",
"clli": "cloud_site name, must align to cloud-region-id in AAI",
"aic_version": "2.5",
"identity_service_id": "DEFAULT_KEYSTONE2"
}
}
}
}
3, Change Robot service to operate with the VIM/Cloud instance
By default the Robot service supports the pre-populated cloud region of which the cloud-owner is "CloudOwner" and cloud-region-id is specified via the parameters "openstack_region" for deploying this ONAP instance. All cloud region information can be found at "/share/config/vm_properties.py" .
Robot service supports the hacking operations to populate subscribers, service models, and preload VNF data, bridge heat instance into AAI, as well as APPC mount. Most of operation are tightly coupled with the default cloud region. So if you would like to perform such hacking operations with additional cloud region, you'd better to launch another robot VM with corresponding cloud region parameters in order to get expected results.
Please refer to the template to create additional robot for new cloud region
Hint: Take care of following parameters which should reflect the new cloud region information, while others reflect the cloud region where ONAP runs
parameters reflecting info of new cloud region
openstack_tenant_id: PUT YOUR OPENSTACK PROJECT ID HERE
openstack_username: PUT YOUR OPENSTACK USERNAME HERE
openstack_api_key: PUT YOUR OPENSTACK PASSWORD HERE
openstack_region: PUT YOUR OPENSTACK Region ID HERE, e.g. RegionOne
keystone_url: PUT THE KEYSTONE URL HERE (do not include version number)
cloud_env: openstack
To verify if the new robot service works well, you could check the ONAP service health from the new robot VM.
*** ssh to Robot VM and perform following command, it is expected the same output as you can get from the original Robot VM***
sudo docker exec -it openecompete_container /var/opt/OpenECOMP_ETE/runTags.sh -i health h -d ./html -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py -V /share/config/vm_properties.py
