...

This page will walk through the robot framework automated creation of the vFirewall Closed Loop (vFWCL) use case to show how the overall vFWCL works and to high light the confirmation steps and training that can be derived from the robot automated test.

Preconditions:

1. The demonstration VNFs like vFWCL assume that the ONAP OAM network is setup in your environment as a 10.0.0.0/16 with a prefix cidr of 10.0. Robot will assign OAM IP addresses in this range.
2. The demonstration VNF heat templates assume that the PUBLIC neutron network (openStackPublicNetId) provided in the robot section of the override.yaml  / values.yaml chart is setup so that new interfaces can be created via the VNF Heat template on that public interface. It need not be an external public network and many environments use  a separate external network with floating IPs to assign an external IP to the VNFs external facing ip address/ports after instantiation if they have that setup.
3. ONAP has been installed

...

2. robot init

...

1. has been run ((e.g., ./demo-k8s.sh onap init)) to setup the customer , cloud configurations, distribution of models  and set the owning entity/project/line of business  in VID for tracking the Service and VNF
2. Additionally a distribution

...

1. should  be run

...

1. ( ./ete-k8s.sh onap healthdist) to confirm that model distribution succeeds

cd /root/onap/kubernetes/robot
./ete-k8s.sh onap health
./ete-k8s.sh onap healthdist
./demo-k8s.sh onap init
./demo-k8s.sh onap init_robot  

...

Select one of the test cases from the list and then open log.html (e.g., http://<k8host-ip>:30209/logs/0005_ete_instantiateVFWCL/log.html )

View filenameTestsuites Test Log vFWCL TestsuitesTestLogvFWCL_Dublin.htmhtml

height150Image Added

./ete-k8s.sh onap instantiateVFWCL 

...