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.
...
- 100.1 Starting Mininet Topology - PASS
- 100.2 Connect switches to controller - PASS
- 100.3 Set up tunnel from Mininet node to onos node - PASS
commit b0e1dd018a160134bc8fdd874a787f2bad3fc6dd dd415c31d8a0d57fbe4a3ab721e2a95d7afa4495 (HEAD, origin/onos-1.3, onos-1.3)
Author: Jonathan Hart [jono@onlab.us]
AuthorDate: Wed Sep 23 17:54:11 2015 -0700Mon Nov 16 10:56:20 2015 -0800
Commit: Jonathan Hart [jono@onlab.us]
CommitDate: Thu Sep 24 13:22:23 2015 -0700
IntentManager: Don't compile all failed intents on every eventMon Nov 16 14:14:24 2015 -0800
Protect against exceptions thrown in application's packet processors.
Case 101: Setting up test environment - PASS
...
- 7.1 Stop sw32 - PASS
- 7.2 Check routes installed - PASS
- 7.3 Check M2S intents installed - PASS
- 7.4 Check P2P intents installed - PASS
- 7.5 Check ping between hosts behind BGP peers - PASS
- 7.6 Check ping between BGP peers and speakers - PASS
- 7.7 Check whether all flow status are ADDED - PASS
Case 8: Start the edge sw32, check P-2-P and M-2-S intents, ping test -
...
PASS
- 8.1 Start sw32 - PASS
- 8.2 Check routes installed - PASS
- 8.3 Check M2S intents installed - PASS
- 8.4 Check P2P intents installed - PASS
- 8.5 Check whether all flow status are ADDED - PASS
- 8.6 BGP speakers ping peers, expect all tests to succeed - PASS
- 8.7 Check ping between each host pair - FAIL
- PASS
Case 9: Stop sw11 located in best path, check route number, P2P intent number, M2S intent number, ping test - PASS
...