Charles Chan | caebcf3 | 2021-09-20 22:17:52 -0700 | [diff] [blame] | 1 | System Integration Test (TestON) |
| 2 | ================================ |
Jon Hall | ced4be7 | 2021-10-04 10:19:04 -0700 | [diff] [blame] | 3 | |
| 4 | Each component of SD-Fabric has it's own testing infrastructure for component level tests. However, we need a way to |
| 5 | test all the components together. For SD-Fabric, we are using a framework called `TestON`_ to write these tests. We |
| 6 | use TestON to manipulate the components via CLI sessions over ssh or rest APIs. More information on how TestON works |
| 7 | can be found in the `TestON Guide`_. The dataplane for these tests are either an emulated network running in Mininet |
| 8 | using software switches, or hardware pods located in our lab. We use a variety of traffic generation tools running |
| 9 | on the hosts to create traffic in the fabric. |
| 10 | |
| 11 | The current :ref:`topology<Topology>` for the hardware pod used for integration test is a set of leaf pair switches, |
| 12 | a dual homed management server, and 3 compute nodes. One compute node is dual homed, one is dual homed with a second |
| 13 | link to the second leaf switch, and one single homed to the second leaf switch. |
| 14 | |
| 15 | .. image:: ../images/paired-leaves-pod.svg |
| 16 | :scale: 100 |
| 17 | |
| 18 | We also run soak testing and failure/recovery test in a 2x2 hardware pod. |
| 19 | |
| 20 | .. image:: ../images/topology-2x2.png |
| 21 | :width: 300px |
| 22 | |
| 23 | Test Suites |
| 24 | ----------- |
| 25 | |
| 26 | * Functionality Tests |
| 27 | |
| 28 | * `Paired Leaves <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/SRStaging/SRpairedLeaves>`_ |
| 29 | |
| 30 | * Basic Connectivity - All hosts can ping each other and their fabric interfaces. |
| 31 | |
| 32 | * Link Failure - Verify a traffic stream fails over when there is a link failure. We test both failure of both |
| 33 | the source and destination links for dual and single homed hosts. |
| 34 | |
| 35 | * Switch Failure - Verify a traffic stream fails over when there is a switch failure. We test several device |
| 36 | failure modes for both the source and destination leaves for dual and single homed hosts. |
| 37 | |
| 38 | * `Bridging <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/SRBridging>`_ - Verify bridging works between different host VLAN configurations. |
| 39 | |
| 40 | * `Routing <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/SRRouting>`_ - Verify routing works with different route configurations. |
| 41 | |
| 42 | * `INT <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/INT>`_ - Verify INT reports for different packet drop reasons. |
| 43 | |
| 44 | * `UPF <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/UP4>`_ - Tests ONOS UP4 APIs, such as attachment and detachment of UEs as well as verify encapsulation of both |
| 45 | upstream and downstream traffic. |
| 46 | |
| 47 | * QOS |
| 48 | |
| 49 | * `QOS <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/QOS>`_ - Generate traffic flows with different QFIs and verify QOS using port statistics. |
| 50 | |
| 51 | * `QOSNonMobile <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/QOSNonMobile>`_ - Generate traffic flows with non mobile Traffic Classification and verify QOS using port statistics. |
| 52 | |
| 53 | * Failure/Recovery Tests |
| 54 | |
| 55 | * Link Failure Tests - Setup a flow from between hosts connected to different leaves, disable a link between a |
| 56 | leaf and a spine used by the flow, verify and measure how fast the flow is rerouted to another link. |
| 57 | |
| 58 | * `Access Leaf <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/SRStaging/SReNBLeafSpinePortstateFailure>`_ - Disable a link between the access leaf and a spine. |
| 59 | |
| 60 | * `Upstream Leaf <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/SRStaging/SRupstreamLeafSpinePortstateFailure>`_ - Disable a link between the upstream lead and a spine. |
| 61 | |
| 62 | * Switch Failure Tests - Setup a flow from between hosts connected to different leaves, disable a spine used by |
| 63 | the flow, verify and measure how fast the flow is rerouted to another spine. |
| 64 | |
| 65 | * `ONL Reboot <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/SRStaging/SRONLReboot>`_ - Simulate a switch failure by restarting ONL on the switch. |
| 66 | |
| 67 | * `Stratum Restart <https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON/tests/USECASE/SegmentRouting/SRStaging/SRstratumRestart>`_ - Simulate a switch failure by killing the stratum agent on the switch. |
| 68 | |
| 69 | |
| 70 | Test Results |
| 71 | ------------ |
| 72 | |
| 73 | The nightly test results can be found by looking at the `SD-Fabric Nightly Tests`_ view on the `Aether Jenkins`_ |
| 74 | website. The functionality test suites are run on the Paired Leaves Pod and the failure/recovery jobs are run on the |
| 75 | Staging Pod. |
| 76 | |
| 77 | .. _SD-Fabric Nightly Tests: https://jenkins.aetherproject.org/view/SD-Fabric%20Nightly%20Tests/ |
| 78 | .. _Aether Jenkins: https://jenkins.aetherproject.org/login |
| 79 | .. _TestON: https://github.com/opennetworkinglab/OnosSystemTest/tree/master/TestON |
| 80 | .. _TestON Guide: https://wiki.onosproject.org/display/ONOS/System+Testing+Guide |