...
- Running "ete stability72hr" Robot suite hourly. This test suite verifies that ONAP can instantiate vDNS, vFWCL, and VVG.
- Set up vFW Closed Loop to remain running, then check hourly that the closed loop functionality is still working.
Stability72hr Test Suite
From the Rancher VM, log in as root, and run:
| Code Block |
|---|
/root/oom/kubernetes/robot/ete-k8s.sh onap stability72hr |
Known issues
: On the Wind River lab, openstack will occasionally fail to deploy the stacks due to error like "missing credentials". This appears to be an infrastructure issue.
vFWCL Stability Testing
First, set up vFW Close Loop. Assuming that you have a freshly deployed ONAP, follow the instructions below in sequence:
...
| Code Block |
|---|
# restart drools kubectl execdelete -itpod dev-policy-drools-0 -- bash -c 'source /opt/app/policy/etc/profile.d/env.sh; policy stop' kubectl exec -it dev-policy-drools-0 -- bash -c 'source /opt/app/policy/etc/profile.d/env.sh; policy start'n onap |
The update policies could take 15 to 20 minutes to kick in. So, wait a while:
...
Now, to verify that the vFW Closed Loop is working; be sure to pass in the public IP address of the Packet Generator as the variable $PNG_IP:
| Code Block |
|---|
# demo vfwclosedloop /root/oom/kubernetes/robot/demo-k8s.sh onap vfwclosedloop $PNG_IP |
You can watch the packets by going to the Sink VM IP port 667 using a browser.
Known Issues
The VPP stack in the Packet Generator will freeze after running for about a day or so. This can be fixed by rebooting the Packet Generator VM. For long-running tests, it would be advisable to reboot the Packet Generator every 12 hours or so.