...
commit a69534f1694e2b8e190e6eb96513843846e19e93 a09c0ed8a2e652c26cbaf34f8147d3b65b30dff0 (HEAD, origin/master, origin/HEAD, master)
Author: Sahil Lele Thomas Vachuska [sahil@onlabtom@onlab.us]
AuthorDate: Thu Fri Jul 16 1517 18:1458:57 55 2015 -0700
Commit: Sahil Lele Thomas Vachuska [sahil@onlabtom@onlab.us]
CommitDate: Fri Jul 17 1518:1858:40 55 2015 -0700
ONOS-2379 Reactive Fwd improvements prune bad flows from switches when a link goes down
Fixed listener registry to eject listeners only if they indeed exceed the limit.
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> |
...
- 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
- PASS
- 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
FAIL
- Intent ECM anti-entropy took too long
Case 8: Compare ONOS Topology view to Mininet topology - PASS
...
- 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
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 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 Wait a minute then ping again - PASS
ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 15: Check that Leadership Election is still functional - PASS
...
- 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
...
- 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
...
- 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
FAIL
- Intents are not all in INSTALLED state
- 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 - PASS
- 12.1 Add back s5 - 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 - 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
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
FAIL
- Intents are not all in INSTALLED state
- 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
...