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 df6372b604ea521828787663bbd863ecbd61b895 e18a2ef92e30e4575bb76c06e1e6004d36180e30 (HEAD, origin/master, origin/HEAD, master)
Author: Hyunsun Moon [hyunsun.moon@gmailYuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Thu Mon Jul 7 1711 23:3734:20 38 2016 -0700
Commit: Gerrit Code Review [gerrit@onlab.usYuta HIGUCHI [y-higuchi@ak.jp.nec.com]
CommitDate: Fri Jul 8 17Mon Jul 11 23:34:38 :36 2016 +0000
Chagned drivers/ovsdb app name to avoid conflict with providers/ovsdb-0700
Fix javadoc error
| 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 8 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
- 7.6 Compare current intents with intents before the failure - PASS
- 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
Case 4: Verify connectivity by sending traffic across Intents -
...
PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - FAIL
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
- PASS
Case 15: Check that Leadership Election is still functional - 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