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 5f8893092a82dded627806b086fef68e1c3fb394 d3c2d7419e859e6b92e9fbb21a7704193cccc016 (HEAD, origin/onos-1.9, onos-1.9)
Author: Luca Prete Ray Milkey [luca@onlabray@onlab.us]
AuthorDate: Thu Mar 23 10:26:16 Mon May 1 16:00:53 2017 -0700
Commit: Luca Prete Ray Milkey [luca@onlabray@onlab.us]
CommitDate: Mon Apr 24 23:48:40 Tue May 2 19:42:03 2017 +0000
Updating and fixing vagrant ONOS VM
Fix filtering of UI archetype java files
--
(cherry picked from commit 14b62a08da1b1051f23ed683840d1615b67f62c9)
Case 101: Setting up ONOS environment - PASS
...
- 5.1 Bring down the link between sw32 and p64514 - PASS
- 5.2 Check routes installed - PASS
- 5.3 Check M2S intents installed - PASS
- 5.4 Bring down the link between sw8 and p64515 - PASS
- 5.5 Check routes installed - PASS
- 5.6 Check M2S intents installed - PASS
- 5.7 Bring down the link between sw28 and p64516 - PASS
- 5.8 Check routes installed - PASS
- 5.9 Check M2S intents installed - 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
Case 6: Bring up links and check routes/intents -
...
FAIL
- 6.1 Bring up the link between sw32 and p64514 - PASS
- 6.2 Check routes installed - PASS
- 6.3 Check M2S intents installed - PASS
- 6.4 Bring up the link between sw8 and p64515 - PASS
- 6.5 Check routes installed - PASS
- 6.6 Check M2S intents installed - PASS
- 6.7 Bring up the link between sw28 and p64516 - 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
...
- 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 BGP speakers ping peers, expect all tests to succeed - PASS
- 8.8 Check ping between each host pair, expect all to succede=True - PASS
Case 9: Stop sw11 located in best path, check route number, P2P intent number, M2S intent number, ping test - FAIL
- 9.1 Check flow entry number in sw11 - PASS
- 9.2 Check flow entry number in sw1 - FAIL
- Flow number in sw1 is wrong!
- 9.3 Check flow entry number in sw7 - PASS
- 9.4 Stop sw11 - PASS
- 9.5 Check routes installed - PASS
- 9.6 Check M2S intents installed - PASS
- 9.7 Check P2P intents installed - PASS
- 9.8 Check whether all flow status are ADDED - PASS
- 9.9 BGP speakers ping peers, expect all tests to succeed - PASS
- 9.10 BGP speakers ping peers, expect all tests to succeed - PASS
- 9.11 Check ping between each host pair, expect all to succede=True - PASS
Case 10: Start sw11 which was stopped in CASE9, check route number, P2P intent number, M2S intent number, ping test - FAIL
- 10.1 Check flow entry number in sw1 - FAIL
- Flow number in sw1 is wrong!
- 10.2 Check flow entry number in sw7 - FAIL
- Flow number in sw7 is wrong!
- 10.3 Start sw11 - PASS
- 10.4 Check routes installed - PASS
- 10.5 Check M2S intents installed - PASS
- 10.6 Check P2P intents installed - PASS
- 10.7 Check whether all flow status are ADDED - PASS
- 10.8 BGP speakers ping peers, expect all tests to succeed - PASS
- 10.9 BGP speakers ping peers, expect all tests to succeed - PASS
- 10.10 Check ping between each host pair, expect all to succede=True - PASS