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.
...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric/lastSuccessfulBuild/artifact/HAbackupRecover_master_20-builds_graph.jpg", alt="HAbackupRecover", style="width:525px;height:350px;border:0"> |
commit da3b9f09807e4054835495b1d61b3956ef5c5cbd 022ec275e540309752c2f6af9e9b10655357cce1 (HEAD -] master, origin/master, origin/HEAD)
Author: Jordan Halterman [jordan@opennetworking.orgSean Condon [sean.condon@microsemi.com]
AuthorDate: Fri Wed Oct 5 1310 09:2857:51 05 2018 -0700+0100
Commit: Charles Chan [charles@opennetworking.orgSean Condon [sean.condon@microsemi.com]
CommitDate: Tue Wed Oct 9 1710 09:2457:35 05 2018 +0000
Avoid closing DeviceFlowTable when flows are purged on device down event
--
(cherry picked from commit cd4276521ca0a7268353317ede37de33cdbe4c52)0100
Added a scroll bar to Nav Menu for GUI and GUI2
Case 1: Starting up 7 node(s) ONOS cluster - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 5: Setting up and gathering data for current state -
...
FAIL
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch from each controller - No Result
- 5.3 Read device roles from ONOS - PASS
- 5.4 Check for consistency in roles from each controller - PASS FAIL
- ONOS nodes have different views of switch roles
- 5.5 Get the intents from each controller - PASS
- 5.6 Check for consistency in Intents from each controller - PASS
- 5.7 Get the flows from each controller - PASS
- 5.8 Check for consistency in Flows from each controller - PASS
- 5.9 Get the OF Table entries - No Result
- 5.10 Start continuous pings - No Result
- 5.11 Collecting topology information from ONOS - No Result
- 5.12 Host view is consistent across ONOS nodes - PASS
- 5.13 Each host has an IP address - PASS
- 5.14 Cluster view is consistent across ONOS nodes - PASS
- 5.15 Cluster view correct across ONOS nodes - PASS
- 5.16 Comparing ONOS topology to MN - PASS
- 5.17 Device information is correct - PASS
- 5.18 Links are correct - PASS
- 5.19 Hosts are correct - PASS
...
- 6.1 Backup ONOS data - PASS
- 6.2 Checking ONOS Logs for errors - No Result
- 6.3 Uninstalling ONOS package - PASS
- 6.4 Installing ONOS package - PASS
- 6.5 Restore ONOS data - PASS
- 6.6 Restart ONOS nodes - No Result
- 6.7 Set up ONOS secure SSH - PASS
- 6.8 Checking ONOS service - PASS
- 6.9 Starting ONOS CLI sessions - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - FAIL
- Nodes check NOT successful
- PASS
Case 7: Running ONOS Constant State Tests - PASS
...
- 7.1 Check that each switch has a master - PASS
- 7.2 Read device roles from ONOS - PASS
- 7.3 Check for consistency in roles from each controller - PASS
- 7.4 Get the intents from each controller - PASS
- 7.5 Check for consistency in Intents from each controller - PASS
- 7.6 Leadership Election is still functional - PASS
Case 104: Check connectivity -
...
PASS
- 104.1 Ping
- 104.1 Ping between all hosts - FAIL Failed to ping
- between all hosts - PASS
Case 15: Check that Leadership Election is still functional - PASS
...
- 9.1 Kill Link between spine102 and leaf1 - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - FAIL
- Nodes check NOT successful
- PASS
Case 104: Check connectivity -
...
PASS
- 104.1 Ping between all hosts - FAIL Failed to ping between all hosts
- PASS
Case 10: Restore a link to ensure that Link Discovery is working properly - PASS
...
- 10.1 Bring link between spine102 and leaf1 back up - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - FAIL
- Nodes check NOT successful
- PASS
Case 104: Check connectivity -
...
PASS
- 104.1 Ping between all hosts - FAIL Failed to ping between all hosts
- PASS
Case 13: Test Cleanup - PASS
...