Page History

...

commit 3f1b128b17114ce081206191ea8472a16b13ddf9 0c41ba26a900107788532b29649a671a83bfe6ec (HEAD, origin/master, origin/HEAD, master)
Author: Kenji HIKICHI [hikichi.kenji@jp.fujitsu.comBri Prebilic Cole [bri@onlab.us]
AuthorDate: Fri Mon Jul 3 176 15:4009:09 48 2015 +0900-0700
Commit: Gerrit Code Review [gerrit@onlabBri Prebilic Cole [bri@onlab.us]
CommitDate: Sat Mon Jul 4 006 15:3809:32 56 2015 +0000
Compare logDir by using File object to avoid test failure on Windows which uses '\' as file separator-0700

GUI -- Cleaned up directives - onos-sortable-header and icon no longer use isolate scope. Icon directive moved to icon.js. Deleted unneeded TableService.

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

...

Compare topology objects between Mininet and ONOS

...

• 8.2 1 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 9 Links are correct - PASS
• 8.11 Links 10 Hosts are correct - PASS
• 8.12 11 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 9 Links are correct - PASS
• 8.11 Links 10 Hosts are correct - PASS
• 8.12 11 Checking ONOS nodes - PASS

...

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

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 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 - FAIL
Topology Check Test NOT successful
• - PASS
• 5.16 Device information is correct - PASS
• 5.17 Links are correct - PASS
• 5.18 Hosts are correct - PASS

Case 14: Start Leadership Election app - PASS

...

Case 6: Wait 60 seconds instead of inducing a failure - 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 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 9 Links are correct - FAIL
• Port information is incorrect
• PASS
• 8.10 Hosts 8.11 Links are correct - PASS
• 8.12 11 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
• 7.9 Check the continuous pings to ensure that no packets were dropped during component failure - FAIL
Loss of dataplane connectivity detected
• - PASS
• 7.10 Leadership Election is still functional - PASS

...

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

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 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 - FAIL
Port information is incorrect
• 9 Links are correct - PASS
• 8.11 Links 10 Hosts are correct - PASS
• 8.12 11 Checking ONOS nodes - PASS

...

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

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 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 - FAIL
Port information is incorrect
• 9 Links are correct - PASS
• 8.11 Links 10 Hosts are correct - PASS
• 8.12 11 Checking ONOS nodes - PASS

...

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

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 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 - FAIL
Port information is incorrect
• 9 Links are correct - PASS
• 8.11 Links 10 Hosts are correct - PASS
• 8.12 11 Checking ONOS nodes - PASS

...

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

...

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 9 Links are correct - FAIL
• Port information is incorrect
• PASS
• 8.10 Hosts 8.11 Links are correct - PASS
• 8.12 11 Checking ONOS nodes - 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 - FAIL
Some topics were lost
• PASS
• 4.4 Wait a minute then ping again - PASS

...