Table of Contents
outline true

Introduction

...

Virtual deployment

Test Framework

All components are tested with end-to-end testing

...

Tingjie Chen (Deactivated)

SDEWAN

...

Openness

ChenjieXu (Deactivated)

ONAP4K8s:

• ONAP4K8s testing check the health connectivity ONAP Micro service, once it is installed

cFW:

• Cloud Native FW having multiple components such packetgen generator, sink and cFW
  • Packet generator: Sends packets to the packet sink through the firewall. This includes a script that periodically generates different volumes of traffic inside the container
  • Firewall: Reports the volume of traffic passing though to the ONAP DCAE collector.
  • Traffic sink: Displays the traffic volume that lands at the sink container using the link  node port through your browser and enable automatic page refresh by clicking the "Off" button. You can see the traffic volume in the charts.Image Removed

EdgeX Foundry:

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

SDEWAN CNF/Config-Agent:

• 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 serviceUse 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

Openness

ChenjieXu (Deactivated)

ONAP4K8s:

• ONAP4K8s testing check the health connectivity ONAP Micro service, once it is installed

cFW:

• Cloud Native FW having multiple components such packetgen generator, sink and cFW
  • Packet generator: Sends packets to the packet sink through the firewall. This includes a script that periodically generates different volumes of traffic inside the container
  • Firewall: Reports the volume of traffic passing though to the ONAP DCAE collector.
  • Traffic sink: Displays the traffic volume that lands at the sink container using the link  node port through your browser and enable automatic page refresh by clicking the "Off" button. You can see the traffic volume in the charts.Image Added

EdgeX Foundry:

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

BluVal Testing

Igor D.C.

CI logs: 

...