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 eefdedfb506b2ebbb2b8221ca11f392d7e4c99c0 e642f7cf7b3e55a6582ecb7b36912eb96d4d19a3 (HEAD, origin/master, origin/HEAD, master)
Author: Charles Chan [rascov@gmail.comBrian O'Connor [bocon@onlab.us]
AuthorDate: Mon May 23 1618:4533:45 04 2016 -0700
Commit: Gerrit Code Review [gerrit@onlabBrian O'Connor [bocon@onlab.us]
CommitDate: Tue Mon May 24 0023 18:0935:42 29 2016 +0000
Remove redundent byte[].class registration-0700
Bumping version to 1.7.0-SNAPSHOT
| 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> |
...
- 2.1 Assign switches to controllers - 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 - FAIL
- 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
...
- 4.1 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- 4.2 Ping across added host intents - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 5: Setting up and gathering data for current state -
...
PASS
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch from each controller - PASS
- 5.3 Check for consistency in roles from each controller - PASS
- 5.4 Get the intents from each controller - PASS
- 5.5 Check for consistency in Intents from each controller - PASS
- 5.6 Get the flows from each controller - PASS
- 5.7 Check for consistency in Flows from each controller - PASS
- 5.8 Get the OF Table entries - No Result
- 5.9 Start continuous pings - No Result
- 5.10 Collecting topology information from ONOS - No Result
- 5.11 Host view is consistent across ONOS nodes - PASS
- 5.12 Each host has an IP address - PASS
- 5.13 Cluster view is consistent across ONOS nodes - FAIL
- PASS
- 5.14 Cluster view correct across ONOS nodes - PASS
- 5.15 Comparing ONOS topology to MN - PASS
- 5.16 Device information is correct - PASS
- 5.17 Links are correct - PASS
- 5.18 Hosts are correct - PASS
...
- 61.1 Checking ONOS Logs for errors - No Result
- 61.2 Partitioning ONOS nodes - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
...
- 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
- 7.6 Compare current intents with intents before the failure - FAIL
- PASS
- 7.7 Get the OF Table entries and compare to before component failure - FAIL
- PASS
- 7.8 Leadership Election is still functional - FAIL
- Something went wrong with Leadership election
...
- 4.1 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- 4.2 Ping across added host intents - FAIL
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
...
- 62.1 Deleteing firewall rules - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
- 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 - FAIL
- ONOS nodes have different views of hosts
- 8.3 Hosts information is correct - FAIL
- Host information is incorrect
- 8.4 Host attachment points to the network - PASS