Page History

...

commit 92ef154c60eacd67c37be091dcdd8f6408b37113 e10ece06ce17a8eff0786493b5417bb159fa7791 (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska Pingping Lin [tom@onlabpingping@onlab.us]
AuthorDate: Tue Thu Jun 9 11 19:3826:38 24 2015 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Fri Jun 10 0212 05:4232:42 08 2015 +0000
Modified d3.js to use alternate force.tick() invocation for improved speed.
let the XOS IP and port configurable

<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>

...

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS 8.2 Comparing Comparing ONOS topology to MN - No Result
• 8.3 2 Collecting topology information from ONOS - PASS
• 8.4 3 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 4 Hosts information is correct - PASS
• 8.6 5 Host attachment points to the network - PASS
• 8.7 6 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 7 There is only one SCC - PASS
• 8.9 8 Device information is correct - PASS
• 8.10 Port information is correct - PASS 8.11 9 Links are correct - PASS
• 8.12 10 Checking ONOS nodes - PASS

...

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS 8.2 Comparing ONOS topology to MN - No Result
• 8.3 2 Collecting topology information from ONOS - PASS
• 8.4 3 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 4 Hosts information is correct - PASS
• 8.6 5 Host attachment points to the network - PASS
• 8.7 6 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 7 There is only one SCC - PASS
• 8.9 8 Device information is correct - PASS
• 8.10 Port information is correct - PASS 8.11 9 Links are correct - PASS
• 8.12 10 Checking ONOS nodes - 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 Create TestONTopology object - No Result 5.11 Collecting topology information from ONOS - No Result
• 5.12 11 Host view is consistent across ONOS nodes - PASS
• 5.13 12 Each host has an IP address - PASS
• 5.14 13 Cluster view is consistent across ONOS nodes - PASS
• 5.15 14 Cluster view correct across ONOS nodes - PASS
• 5.16 15 Comparing ONOS topology to MN - PASS

...

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS 8.2 Comparing ONOS topology to MN - No Result
• 8.3 2 Collecting topology information from ONOS - PASS
• 8.4 3 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 4 Hosts information is correct - PASS
• 8.6 5 Host attachment points to the network - FAIL
• ONOS did not correctly attach hosts to the network
• 8.7 6 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 7 There is only one SCC - PASS FAIL
• ONOS shows 13 SCCs
• 8.9 8 Device information is correct - PASS 8.10 Port information is correct - PASS FAIL
• Device information is incorrect
• 8.11 9 Links are correct - PASS FAIL
• Links are incorrect
• 8.12 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 FAIL
• Error looking up host ids
• 3.7 Intent Anti-Entropy dispersion - FAIL
• Intent ECM anti-entropy took too long

...

• 4.1 Ping across added host intents - 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 - FAIL
• Intents have not been installed correctly, pings failed.

...

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS 8.2 Comparing ONOS topology to MN - No Result
• 8.3 2 Collecting topology information from ONOS - PASS
• 8.4 3 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 4 Hosts information is correct - PASS
• 8.6 5 Host attachment points to the network - FAIL
• ONOS did not correctly attach hosts to the network
• 8.7 6 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 7 There is only one SCC - PASS FAIL
• ONOS shows 17 SCCs
• 8.9 8 Device information is correct - PASS 8.10 Port information is correct - PASS FAIL
• Device information is incorrect
• 8.11 9 Links are correct - PASS FAIL
• Links are incorrect
• 8.12 10 Checking ONOS nodes - PASS

...

• 4.1 Ping across added host intents - 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 - FAIL
• Intents have not been installed correctly, pings failed.

...

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS 8.2 Comparing ONOS topology to MN - No Result
• 8.3 2 Collecting topology information from ONOS - PASS
• 8.4 3 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 4 Hosts information is correct - PASS
• 8.6 5 Host attachment points to the network - FAIL
• ONOS did not correctly attach hosts to the network
• 8.7 6 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 7 There is only one SCC - PASS FAIL
• ONOS shows 17 SCCs
• 8.9 8 Device information is correct - PASS 8.10 Port information is correct - PASS FAIL
• Device information is incorrect
• 8.11 9 Links are correct - PASS FAIL
• Links are incorrect
• 8.12 10 Checking ONOS nodes - PASS

...

• 4.1 Ping across added host intents - 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 - FAIL
• Intents have not been installed correctly, pings failed.

...

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS 8.2 Comparing ONOS topology to MN - No Result
• 8.3 2 Collecting topology information from ONOS - PASS
• 8.4 3 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 4 Hosts information is correct - PASS
• 8.6 5 Host attachment points to the network - FAIL
• ONOS did not correctly attach hosts to the network
• 8.7 6 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 7 There is only one SCC - FAIL
• ONOS shows 2 16 SCCs
• 8.9 8 Device information is correct - PASS 8.10 Port information is correct - PASS FAIL
• Device information is incorrect
• 8.11 9 Links are correct - FAIL
• Links are incorrect
• 8.12 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 - 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 - 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 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - FAIL
• ONOS did not correctly attach hosts to the network
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - FAIL
• ONOS shows 2 SCCs
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - FAIL
• Links are incorrect
• 8.12 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 - 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 - FAIL
• Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

• 13.1 Killing tcpdumps - No Result
• 13.2 Copying MN pcap and ONOS log files to test station - No Result
• 13.3 Stopping Mininet - PASS
• 13.4 Checking ONOS Logs for errors - No Result
• 13.5 Packing and rotating pcap archives - No Result