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 93c8f9e77606cf5f68d74d0e3ade2026fa639bc6 c1e4e4c67a0642a6c315c65c2efb7552fb5698b9 (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska [tom@onlab.usPriyanka B [priyanka.b@huawei.com]
AuthorDate: Sat Fri Jul 2 121 14:5957:44 19 2016 +02000530
Commit: Thomas Vachuska [tom@onlab.usPriyanka B [priyanka.b@huawei.com]
CommitDate: Sat Tue Jul 2 125 13:5900:44 55 2016 +0200
Changing label from Switches to Devices0530
[ONOS] cherry picked from 1.6, bandwidth, CR and resilency fix
| HTML |
|---|
<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=1&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 61.1 Checking ONOS Logs for errors - No Result
- 61.2 Partitioning ONOS nodes - PASS
- 61.3 Sleeping 60 seconds - No Result
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS FAIL
- ONOS topology don't match Mininet
- 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 FAIL
- ONOS shows 4 SCCs
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS FAIL
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - 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 and compare across all nodes - PASS
- 7.5 Check for consistency in Intents from each controller - PASS FAIL
- ONOS nodes have different views of intents
- 7.6 Compare current intents with intents before the failure - PASS FAIL
- The Intents changed during failure
- 7.7 Get the OF Table entries and compare to before component failure - FAIL
- Changes were found in the flow tables
- 7.8 Leadership Election is still functional - PASS
...
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.2 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
...
- 62.1 Deleteing firewall rules - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 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 - FAIL
- ONOS nodes have different views of hostsclusters
- 8.6 There is only one SCC - PASS
- 8.3 Hosts 7 Device information is correct - PASS
- 8.8 Links are correct - FAIL
- Host information is incorrect
- Links are incorrect
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 7: Running ONOS Constant State Tests - FAIL
- 7.1 Check that each switch has a master - FAIL
- Some devices don't have a master assigned
- 7.2 Read device roles from ONOS - FAIL
- Error in reading roles from ONOS
- 7.3 Check for consistency in roles from each controller - FAIL
- ONOS nodes have different views of switch roles
- 7.4 Get the intents and compare across all nodes - FAIL
- Error in reading intents from ONOS