Page History

...

commit 08fdbd2302a37806a37623d814173f6086db460b 4fc8685ee2cde5ac660cb06ea9bf545754594fda (HEAD, origin/master, origin/HEAD, master)
Author: Sho SHIMIZU Simon Hunt [sshimizu@ussimon@onlab.fujitsu.comus]
AuthorDate: Wed Thu Aug 19 1620 17:5957:35 52 2015 -0700
Commit: Gerrit Code Review [gerrit@onlabSimon Hunt [simon@onlab.us]
CommitDate: Thu Aug 20 0017:5159:25 18 2015 +0000-0700

ONOS-2691: Register a port as resource when is is added-2186 - GUI Topo Overlay - (WIP)

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

...

• 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 - PASS
• 7.7 Compare current intents with intents before the failure - PASS
• 7.8 Get the OF Table entries and compare to before component failure - PASS
• 7.9 Leadership Election is still functional - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

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.
• - PASS
• 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.
• PASS

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 Hosts are correct - PASS
• 8.11 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

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.
• PASS
• 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.
• 4.4 Wait a minute then ping again - PASS

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 - FAIL
• Links are incorrect
• 8.10 Hosts are correct - PASS
• 8.11 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

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.
• PASS
• 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.
• PASS

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 Hosts are correct - PASS
• 8.11 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

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.
• PASS
• 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.
• 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 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 Hosts are correct - PASS
• 8.11 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

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.
• PASS
• 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.
• PASS

Case 13: Test Cleanup - PASS

...