...
EdgeX Foundry helm chart are installed through ONAP in the edge location. Test case ensure that all the EdgeX Framework containers are up and running
SDWAN controller:
SDEWAN CNF:
- Use Kud to setup 3 clusters (traffic hub, edge1, edge2)
- Create SDEWAN CNF instance and dummy pod in edge1, SDEWAN CNF instance and httpbin pod in edge2
- Configure traffic hub as responder to provide IP addresses to any authenticated party requesting for IP addresses.
- Configure edge1 and edge2 IPSec configuration to get the IP addresses.
- Establish edge1 tunnel to traffic hub, edge2 tunnel to hub, and hub policy for traffic between edge1 and edge2
- Establish SNAT rule in edge1 and DNAT rule in edge2 to enable tcp connection from edge1 to edge2's httpbin service
- Verify curl command is successful from edge1 dummy pod to edge2's httpbin service
- Create SDWAN CNF and a normal pod with additional interfaces created by OVN CNI plugin, and verify ping is workable between these 2 pods through the OVN interfaces
- Disable Allow-Ping rule of SDWAN CNF through Command Rest API call, then verify ping is not work between these 2 pods through the OVN interfaces
- Enable Allow-Ping rule of SDWAN CNF through Command Rest API call, then verify ping is workable again between these 2 pods through the OVN interfaces
CI logs:
The gerrit comments contains the CI log url. All the CI logs are under this folder ICN : https://jenkins.akraino.org/view/icn/job/icn-master-verify/
...