Page History

...

commit bfc8b7a973a43b3e984877735235406499e8fb3f 5f5d281432c9f28465ebdce4b23470d0b23134e7 (HEAD, origin/master, origin/HEAD, master)
Author: HIGUCHI Yuta [y-higuchi@ak.jp.necalshabib [alshabibi.ali@gmail.com]
AuthorDate: Wed Thu Jul 1 232 18:4743:43 19 2015 -0700
Commit: HIGUCHI Yuta [y-higuchi@ak.jp.necalshabib [alshabibi.ali@gmail.com]
CommitDate: Wed Thu Jul 1 232 18:5243:17 19 2015 -0700
Utility method to treat Iterable as a Stream
Reverting change to IdBlockGenerator that caused NPE when installing flows.

<iframe src="https://onos-jenkins.onlab.us/job/HASanity/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 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 - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - FAIL
• ONOS shows 2 SCCs
• PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS
• 8.11 Links are correct - FAIL
• Links are incorrect
• PASS
• 8.12 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches -

...

FAIL

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

• 21.1 Assign mastership of switches to specific controllers - PASS
• 21.2 Check mastership was correctly assigned - PASS FAIL
• Switches were not successfully reassigned

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 - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - FAIL
• ONOS shows 2 SCCs
• PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS FAIL
• Port information is incorrect
• 8. 8.11 Links are correct - FAIL
• Links are incorrect
• PASS
• 8.12 Checking ONOS nodes - PASS

...

• 4.1 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS FAIL
• Some topics were lost
• 4.4 Wait a minute then ping again - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 5: Setting up and gathering data for current state - FAIL

...

• 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 - FAIL
• ONOS nodes have different views of intents
• 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 Host view is consistent across ONOS nodes - PASS
• 5.13 Each host has an IP address - PASS
• 5.14 Cluster view is consistent across ONOS nodes - PASS
• 5.15 Cluster view correct across ONOS nodes - FAIL
• ONOS shows 2 SCCs
• PASS
• 5.16 Comparing ONOS topology to MN - FAIL
• Topology Check Test NOT successful

...

Case 6: Wait 60 seconds instead of inducing a failure - 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 - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - FAIL
ONOS shows 2 SCCs
• PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS FAIL
• Port information is incorrect
• 8.11 Links are correct - FAIL
Links are incorrect
• PASS
• 8.12 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 Compare switch roles from before failure - PASS
• 7.5 Get the intents and compare across all nodes - PASS
• 7.6 Check for consistency in Intents from each controller - FAIL
• ONOS nodes have different views of intents
• 7.7 Compare current intents with intents before the failure - FAIL
• The Intents changed during failure
• 7.8 Get the OF Table entries and compare to before component failure - PASS FAIL
• Changes were found in the flow tables
• 7.9 Check the continuous pings to ensure that no packets were dropped during component failure - PASS FAIL
• Loss of dataplane connectivity detected
• 7.10 Leadership Election is still functional - PASS

...

• 4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS FAIL
• Some topics were lost
• 4.4 Wait a minute then ping again - PASS

...

• 9.1 Kill Link between s3 and s28 - 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 - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - FAIL
ONOS shows 3 SCCs
• PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS FAIL
• Port information is incorrect
• 8.11 Links are correct - FAIL
Links are incorrect
• PASS
• 8.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
• 4.3 Check leadership of topics - PASS FAIL
• Some topics were lost
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

...

• 10.1 Bring link between s3 and s28 back up - 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 - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - FAIL
ONOS shows 2 SCCs
• PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - PASS FAIL
• Port information is incorrect
• 8 8.11 Links are correct - FAIL
• Links are incorrect
• 8.12 Checking ONOS nodes - PASS

...

• 4.1 Ping across added host intents - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS FAIL
• Some topics were lost
• 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 - FAIL

...

• 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 - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - FAIL
• ONOS shows 3 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 - PASS
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS

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 - PASS
• 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 - PASS
• 4.2 Check Intent state - FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS

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