Page History

...

commit e10ece06ce17a8eff0786493b5417bb159fa7791 f65c378e68a5a73caece73652e9a00693dcdaffd (HEAD, origin/master, origin/HEAD, master)
Author: Pingping Lin Simon Hunt [pingping@onlabsimon@onlab.us]
AuthorDate: Thu Fri Jun 11 1912 13:2633:24 48 2015 -0700
Commit: Gerrit Code Review [gerrit@onlabSimon Hunt [simon@onlab.us]
CommitDate: Fri Jun 12 0513:3233:08 48 2015 +0000
let the XOS IP and port configurable
-0700

GUI -- Topo View - change default map to be continental US.

<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 ONOS topology to MN - No Result
• 8.2 3 Collecting topology information from ONOS - PASS
• 8.3 4 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 5 Hosts information is correct - PASS
• 8.5 6 Host attachment points to the network - PASS
• 8.6 7 Clusters view is consistent across all ONOS nodes - PASS
• 8.7 8 There is only one SCC - PASS
• 8.8 Device 9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.9 11 Links are correct - PASS
• 8.10 12 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
• 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 8Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

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

Case 7: Running ONOS Constant State Tests - FAIL

...

• 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 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.2 3 Collecting topology information from ONOS - PASS
• 8.3 4 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 5 Hosts information is correct - PASS
• 8.5 6 Host attachment points to the network - FAIL
• ONOS did not correctly attach hosts to the network
• 8.6 7 Clusters view is consistent across all ONOS nodes - PASS
• 8.7 8 There is only one SCC - FAIL
ONOS shows 17 SCCs
• PASS
• 8.8 9 Device information is correct - FAIL
Device information is incorrect
• PASS
• 8.10 Port information is correct - PASS
• 8.9 11 Links are correct - FAIL
• Links are incorrect
• PASS
• 8.10 12 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 - 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.

...

Compare topology objects between Mininet and ONOS

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

...

Compare topology objects between Mininet and ONOS

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