...
commit 375f4be24a2b1bf84114d254a6e03965d9a604b6 ed804d51445888ea3b7fce38b80c24496b670471 (HEAD, origin/master, origin/HEAD, master)
Author: Charles Chan Simon Hunt [rascov@gmailsimon@onlab.comus]
AuthorDate: Tue Wed Mar 29 1530 09:5351:59 40 2016 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Wed Mar 29 2330 22:2422:57 21 2016 +0000
Add .buckd and buck-out into .gitignore
Initial cut for UI topo model implementation.
| 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> |
...
- 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 - PASS
- 8.6 There is only one SCC - FAIL
- ONOS shows 6 4 SCCs
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 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 - FAIL
- ONOS nodes have different views of intents
- 7.6 Compare current intents with intents before the failure - FAIL
- The Intents changed during failure
- PASS
- 7.7 Get the OF Table entries and compare to before component failure - FAIL
- Changes were found in the flow tables
- PASS
- 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 Ping across added host intents - FAIL
- PASS
- 4.2 Check Intent state - FAIL
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- PASS
Case 15: Check that Leadership Election is still functional - 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 - 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 clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 3 SCCs
- PASS
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- PASS
- 8. 8.9 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 - FAIL
- ONOS nodes have different views of intents
- 7.6 Compare current intents with intents before the failure - 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
Case 4: Verify connectivity by sending traffic across Intents - FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - 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 - 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 - 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 clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 3 SCCs
- PASS
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- PASS
- 8.9 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents - FAIL
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- 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.
...
- 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 clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 3 SCCs
- PASS
- 8. 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- PASS
- 8.9 Checking ONOS nodes - 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 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- PASS
- 4.2 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- PASS
Case 11: Killing a switch to ensure it is discovered correctly - PASS
...
- 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 clusters
- 8.6 There is only one SCC - FAIL
- PASS
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- PASS
- 8.9 Checking ONOS nodes - 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 Ping across added host intents - FAIL
- PASS
- 4.2 Check Intent state - FAIL
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- PASS
Case 12: Adding a switch to ensure it is discovered correctly - PASS
...
- 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 clusters
- 8.6 There is only one SCC - FAIL
- PASS
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- PASS
- 8.9 Checking ONOS nodes - 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 Ping across added host intents - FAIL
- PASS
- 4.2 Check Intent state - FAIL
- PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- PASS
Case 13: Test Cleanup - PASS
...