I see from time to time people having issues to run demo.sh on an vanilla Openstack (vOS for short) environment. Here are the steps which helped us to get demo.sh running on Ocata:
Rackspace Authentication endpoint
If the first FAIL is mentioned as "access", you might try to authenticate against Rackspace, even if you are using your own vOS instance
- ssh into the robot_vm
- Edit /opt/eteshare/config/integration_robot_properties.py
- at about line 30, there is an assignment to GLOBAL_OPENSTACK_KEYSTONE_SERVER
- change this to GLOBAL_OPENSTACK_KEYSTONE_SERVER=http://<your-controller-ip>:5000
- be careful to use the correct scheme (the original scheme is https, your controller might use http)
- be careful to add the port number
Change POST data template
The Rackspage API seems to differ a bit from the vOS API as it adds a some extra fields in the returned JSON. To get the same from vOS, you need to change the template used for the token request to vOS
- ssh to robot_vm
docker cp openecompete_container:/var/opt/OpenECOMP_ETE/robot/assets/templates/keystone_get_auth.template keystone_get_auth.template
add the tenantName field (be sure not to forget the extra ','); tenant is sometime synonymous used for project in vOS
{
"auth": {
"passwordCredentials": {
"username": "${username}",
"password": "${password}"
},
"tenantName": "<your-tenant-name>"
}
}docker cp keystone_get_auth.template openecompete_container:/var/opt/OpenECOMP_ETE/robot/assets/templates/keystone_get_auth.template
SSL error during run
Sometimes demo.sh fails with ssl errors. If that happens, you can add two lines in the python file to avoid this.
- ssh to robot_vm
docker cp hopenecompete_container:/var/opt/OpenECOMP_ETE/robot/library/RequestsLibrary/RequestsKeywords.py RequestsKeywords.py
- edit RequestsKeywords.py to add two new lines (in red)
import sys
import urllib3
urllib3.disable_warnings(); - docker cp RequestsKeywords.py openecompete_container:/var/opt/OpenECOMP_ETE/robot/library/RequestsLibrary/RequestsKeywords.py