Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
| ID | TestON Case | Description | Environment | Passing Criteria | Roadmap |
|---|---|---|---|---|---|
| 1 | 1 | Basic test to establish functionality
| Using the same mininet script for Dec.5 demo, which includes 4 BGP peers. All bgp routers/speakers are quagga before Dec.5 (We may also use bird after Dec.5) | Test steps: Each BGP peer advertises 10 routes Check the correctness of routes from ONOS CLI Check the correctness of intents from ONOS CLI Ping test for each route (For each route, we will create an relative IP address on the host behind router) All BGP peers withdraw all routes Check the correctness of routes from ONOS CLI Check the correctness of intents from ONOS CLI Ping test for each route | done |
| 2 | 2 | Run a test with a highly fluctuating route stream. Repeat a few times with cycles of intense route fluctuation | Repeat Case1 with cycles of 1000 times | nowdone | |
| 3 | 3 | Scaling test with a large number of peers and routes | Using the same mininet script for Dec.5 demo, but add up to 100 peers | Test steps: Each BGP peer advertises 1000 routes Check the correctness of routes from ONOS CLI Check the correctness of intents from ONOS CLI Ping test for each route All BGP peers withdraw all routes Check the correctness of routes from ONOS CLI Check the correctness of intents from ONOS CLI Ping test for each route | In progressdone |
| 4 | 4 | Simulate an IXP - one peer is a route server advertising routes to other next hops. Run the test with route fluctuation | Based on Case3 Add a route server and a new router and a new host to mininet | The route server advertises 10 routes each time as other BGP peers | In progressdone |
TEST SCENARIOS (MULTIPLE INSTANCES OF SDN-IP/ONOS AND BGP SPEAKERS)
...