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.
...
commit 112ed82fa29981f6ff538e8649d6d33e1d494692 8f45ce2bb931493b25ff77d246460f05b7b3d1a1 (HEAD, origin/master, origin/HEAD, master)
Author: Sithara Punnassery [psithara@gmailSteven Burrows [sburrows@villa-technologies.com]
AuthorDate: Mon Thu Oct 24 1427 20:5504:19 14 2016 -07000500
Commit: Gerrit Code Review [gerrit@onlabSimon Hunt [simon@onlab.us]
CommitDate: Tue Fri Oct 25 1828 01:3112:35 41 2016 +0000
ONOS-5552 DocumentTree builder not available
Fixing reconciling hosts to regions
Case 101: Setting up ONOS environment - PASS
...
- 4.1 Check ping between each host pair, expect all to succede=True - PASS
Case 5: Bring down links and check routes/intents -
...
PASS
- 5.1 Bring down the link between sw32 and peer64514 - PASS
- 5.2 Check routes installed - PASS
- 5.3 Check M2S intents installed - PASS
- 5.4 Bring down the link between sw8 and peer64515 - PASS
- 5.5 Check routes installed - PASS
- 5.6 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- PASS
- 5.7 Bring down the link between sw28 and peer64516 - PASS
- 5.8 Check routes installed - PASS
- 5.9 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- PASS
- 5.10 Check whether all flow status are ADDED - PASS
- 5.11 BGP speakers ping peers, expect all tests to fail - PASS
- 5.12 Check ping between each host pair, expect all to succede=False - PASS
...
- 6.1 Bring up the link between sw32 and peer64514 - PASS
- 6.2 Check routes installed - PASS
- 6.3 Check M2S intents installed - FAIL M2S intent number is wrong!
- PASS
- 6.4 Bring up the link between sw8 and peer64515 - PASS
- 6.5 Check routes installed - PASS
- 6.6 Check M2S intents installed - PASS
- 6.7 Bring up the link between sw28 and peer64516 - PASS
- 6.8 Check routes installed - PASS
- 6.9 Check M2S intents installed - PASS
- 6.10 Check whether all flow status are ADDED - PASS
- 6.11 BGP speakers ping peers, expect all tests to succeed - PASS
- 6.12 Check ping between each host pair, expect all to succede=True - PASS FAIL
- Ping test results are Not expected
Case 7: Stop edge sw32,check P-2-P and M-2-S intents, ping test - PASS
...
- 11.1 Check routes installed - PASS
- 11.2 Check M2S intents installed - PASS
- 11.3 Check P2P intents installed - PASS
- 11.4 Check whether all flow status are ADDED - PASS
- 11.5 BGP speakers ping peers, expect all tests to succeed - PASS
- 11.6 BGP speakers ping peers, expect all tests to succeed - PASS
- 11.7 Check ping between each host pair, expect all to succede=True - PASS
- 11.8 Kill speaker1 - PASS
- 11.9 Check routes installed - PASS
- 11.10 Check M2S intents installed - PASS
- 11.11 Check P2P intents installed - PASS
- 11.12 Check whether all flow status are ADDED - PASS
- 11.13 BGP speakers ping peers, expect all tests to succeed - PASS
- 11.14 Check ping between each host pair, expect all to succede=True - PASS
Case 12: Bring down leader ONOS node, check: route number, P2P intent number, M2S intent number, ping test - PASS
- 12.1 Find out ONOS leader node - No Result
- 12.2 Uninstall ONOS/SDN-IP leader node - PASS
- 12.3 Check routes installed - PASS
- 12.4 Check M2S intents installed - PASS
- 12.5 Check P2P intents installed - PASS
- 12.6 Check whether all flow status are ADDED - PASS
- 12.7 BGP speakers ping peers, expect all tests to succeed - PASS
- 12.8 BGP speakers ping peers, expect all tests to succeed - PASS
- 12.9 Check ping between each host pair, expect all to succede=True - PASS