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 dafa2eedeaa86c80fbce23ec0586c1621cda8e3f 7980d5591fe77f0e9c5582078a9af67a42e8224a (HEAD, origin/onos-1.7, onos-1.7)
Author: Brian O'Connor [bocon@onlab.ussdn [dvaddire@partner.ciena.com]
AuthorDate: Fri Sep 23 14:50:27 Tue Aug 30 04:12:54 2016 -0700
Commit: Brian O'Connor [bocon@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Tue Sep 23 1427 17:5019:27 2016 -0700
Bumping version to 1.7.1-SNAPSHOT07 2016 +0000
Fix for ONOS-5033 hosts - dynamic or static
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 -
...
FAIL
- 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 - PASS
- 5.7 Bring down the link between sw28 and peer64516 - PASS
- 5.8 Check routes installed - PASS
- 5.9 Check M2S intents installed - PASS FAIL
- M2S intent number is wrong!
- 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
Case 6: Bring up links and check routes/intents -
...
FAIL
- 6.1 Bring up the link between sw32 and peer64514 - PASS
- 6.2 Check routes installed - PASS
- 6.3 Check M2S intents installed - PASS FAIL
- M2S intent number is wrong!
- 6.4 Bring up the link between sw8 and peer64515 - PASS
- 6.5 Check routes installed - PASS
- 6.6 Check M2S intents installed - PASS FAIL
- M2S intent number is wrong!
- 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
...
- 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