...
commit 0276a32e8cd7a5cdd0480ad2c570e07f90b8162f 7b438afd38ed9e22d04876679ba0e644c66607a5 (HEAD, origin/master, origin/HEAD, master)
Author: samuel Thomas Vachuska [jiangchuncheng@huaweitom@onlab.comus]
AuthorDate: Mon Tue Jul 13 167 09:3552:17 07 2015 +0800-0700
Commit: Gerrit Code Review [gerrit@onlabThomas Vachuska [tom@onlab.us]
CommitDate: Tue Wed Jul 14 2315 19:1609:30 56 2015 +0000
[ONOS-2374]Add getter method in IpTunnelEndPoint-0700
Initial sketch of the virtual network constructs.
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAClusterRestart/plot/Plot-HA/getPlot?index=0&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 - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - FAIL
- PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - PASS
...
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - FAIL
- Reactive Pingall failed, one or more ping pairs failed
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Intent Anti-Entropy dispersion - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
...
- 6.1 Killing ONOS nodes - PASS
- 6.2 Checking if ONOS is up yet - 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 3: Adding host Intents -
...
FAIL
Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS
- FAIL
- Reactive Pingall failed, one or more ping pairs failed
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Intent Anti-Entropy dispersion - PASS
Case 7: Running ONOS Constant State Tests -
...
FAIL
- 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 Get the OF Table entries and compare to before component failure - PASS
FAIL
- Changes were found in the flow tables
- 7.7 Leadership Election is still functional - PASS
Case 4: Verify connectivity by sendind 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 - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 .4 Wait a minute then ping again - PASS
Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 15: Check that Leadership Election is still functional - PASS
...
- 9.1 Kill Link between s3 and s28 - 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind 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 - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 10: Restore a link to ensure that Link Discovery is working properly - PASS
...
- 10.1 Bring link between s3 and s28 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind 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 - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 11: Killing a switch to ensure it is discovered correctly - PASS
- 11.1 Kill s5 - 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind 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 - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 12: Adding a switch to ensure it is discovered correctly -
...
FAIL
- 12.1 Add back s5 - PASS
- FAIL
- Failed to add switch?
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - PASS
- 8.8 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.9 Links are correct - PASS
FAIL
- Links are incorrect
- 8.10 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sendind 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 - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 13: Test Cleanup - PASS
...