...
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 h openecompete_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
AAI bulk add request getting failed
Rackspace needs tenant id( or may be name and id is same hence doesn’t make a difference in Rackspace) for authentication whereas Openstack Mitaka (we are using Mitaka for Other openstack version this might not be the case ) is using the tenant name for authentication.
Because of which at the Heat Bridge step we were getting authentication error. We changed few python files to overcome this error.
- robot\library\heatbridge\HeatBridge.py (adding extra parameter tenantName )
Before :
def init_bridge(self, openstack_identity_url, username, password, tenant, region, owner):
self.om = OpenstackManager(openstack_identity_url, OpenstackContext(username, password, tenant, region, owner));
self.am = AAIManager(OpenstackContext(username, password, tenant, region, owner));
After :
def init_bridge(self, openstack_identity_url, username, password, tenant, region, owner, tenantName):
self.om = OpenstackManager(openstack_identity_url, OpenstackContext(username, password, tenantName, region, owner,tenantName));
self.am = AAIManager(OpenstackContext(username, password, tenant, region, owner,tenantName));
2. robot\library\heatbridge\OpenstackContext.py (adding extra parameter tenantName )
class OpenstackContext:
"""OpenstackContext is a simple class that holds the provided information that heatbridge uses."""
#this holds the info of the openstack clients
username = None;
password = None;
tenant = None;
region = None;
owner = None;
tenantName= None;
def __init__(self, username, password, tenant, region, owner,tenantName):
self.username = username;
self.password = password;
self.tenant = tenant;
self.region = region;
self.owner = owner;
self.tenantName = tenantName;
3. \robot\resources\heatbridge.robot
Init Bridge ${openstack_identity_url} ${user} ${pass} ${tenant_id} ${region} ${GLOBAL_AAI_CLOUD_OWNER} ${GLOBAL_VM_PROPERTIES['openstack_tenant']}
4. /share/config/vm_properties.py
"openstack_tenant" : "<your tenant Name>",
API version Error
\robot\library\heatbridge\OpenstackManager.py (adding api version)
self.__neutron_client.action_prefix = "/v2.0";
...
/opt/demo.sh appc <DemoModule>
Running ./demo.sh appc DemoModule you might also end up with an error like "error KeyError: 'tenantId'". See a solution from kranthi here: 6591979
Running ./demo.sh appc DemoModule you might also end up with an error like "error KeyError: 'public'". See a solution from kranthi here: 6592019
Heat file changes :
For vfw and vlb we faced few issues related to images we were using. I have attached the heat files here for reference incase you need.
- SSH login was not getting successful during the validation stage so we had to add below lines to the files.
cat /root/.ssh/authorized_keys | awk {'print $14" "$15" "$16'} > /tmp/authorized_keys
cp /tmp/authorized_keys /root/.ssh/authorized_keys
2. Adding default gateway and interface to the iptable
route del -net 0.0.0.0/0
route add -net 0.0.0.0/0 gw <public gateway ip>
echo "auto eth2" >> /etc/network/interfaces
echo "iface eth2 inet dhcp" >> /etc/network/interfaces
echo "auto eth3" >> /etc/network/interfaces
echo "iface eth3 inet dhcp" >> /etc/network/interfaces
ifup eth2
ifup eth3
3. Maven dependency failure with error “Peer not authenticated.” Added below statement to all mvn commands.
mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:get -DremoteRepositories=$REPO_URL_ARTIFACTS -Dartifact=org.openecomp.demo.vnf:sample-distribution:$DEMO_ARTIFACTS_VERSION:tar.gz:hc -Dtransitive=false -Ddest=. -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true
4. Flush all the iptable rules which was filtering the packets from flowing.
iptables -F
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
View file | ||||
---|---|---|---|---|
|