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 1dd60121d8d51ce8bfa021750f8e276b944d1e9a 1b0a39af06ca7f1c7979ad247570b4d0482cf165 (HEAD, origin/master, origin/HEAD, master)
Author: Priyanka B Bharat saraswal [priyankabharat.b@huaweisaraswal@huawei.com]
AuthorDate: Thu Fri Dec 29 16 16:3329:45 02 2016 +0530
Commit: Priyanka B [priyanka.b@huaweibharat saraswal-huawei [bharat.saraswal@huawei.com]
CommitDate: Thu Fri Dec 29 1630 05:3301:58 50 2016 +05300000
[ONOS] Defect fix label downloading for SR-TE-5763] YSR changes to support decode without module name.
Case 101: Setting up ONOS environment - FAIL
...
- 101.1 Copying config files - PASS
- 101.2 Create cell file - No Result
- 101.3 Applying cell variable to environment - PASS
- 101.4 Verify cell connectivity - PASS
- 101.5 Uninstalling ONOS - PASS
- 101.6 Creating ONOS package - PASS FAIL
- Package ONOS failed
- 101.7 Installing ONOS package - PASS FAIL
- Install ONOS to nodes failed
- 101.8 Checking if ONOS is up yet - FAIL
- ONOS nodes are NOT up
- 101.9 Set up ONOS secure SSH - PASS
- 101.10 Checking if ONOS CLI is ready - PASS
- 101.11 Checking if ONOS CLI is ready for issuing commands - 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 - 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
- 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 -
...
PASS
- 6.1 Bring up the link between sw32 and peer64514 - PASS
- 6.2 Check routes installed - PASS
- 6.3 Check M2S intents installed - 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 - FAIL Ping test results are Not expected
- PASS
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 - PASS
- 9.1 Check flow entry number in sw11 - PASS
- 9.2 Check flow entry number in sw1 - PASS
- 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 - PASS
- 10.1 Check flow entry number in sw1 - PASS
- 10.2 Check flow entry number in sw7 - PASS
- 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
Case 11: Kill speaker1, check:route number, P2P intent number, M2S intent number, 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