Page History

...

commit bbc352fe7d829c8b809af8ee3a4c2ca3a43dcdca cfb93e6d4fa5c97477aa78522c811ee6e4e60c69 (HEAD, origin/master, origin/HEAD, master)
Author: Jonathan Hart samueljcc [jono@onlabjiangchuncheng@huawei.uscom]
AuthorDate: Tue Wed Oct 27 1928 15:2457:36 27 2015 -0700
Commit: Gerrit Code Review [gerrit@onlabRay Milkey [ray@onlab.us]
CommitDate: Wed Thu Oct 28 29 02:3554:36 46 2015 +0000
vBNG: Make the compute node to connect point map configurable
[ONOS-3247] Add the junit test code of SubnetId

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

...

• 21.1 Assign mastership of switches to specific controllers - PASS
• 21.2 Check mastership was correctly assigned - 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 FAIL
• ONOS shows 2 SCCs
• 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

...

• 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

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intentintent

• 4.1 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - PASS
• 4.3 Check leadership of topics - PASS
• 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 - 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 - No Result
• 5.11 Host view is consistent across ONOS nodes - PASS
• 5.12 Each host has an IP address - PASS FAIL
• The ip of at least one host is missing
• 5.13 Cluster view is consistent across ONOS nodes - PASS
• 5.14 Cluster view correct across ONOS nodes - PASS FAIL
• ONOS shows 2 SCCs
• 5.15 Comparing ONOS topology to MN - PASS - FAIL
• ONOS7 hosts don't match Mininet
• 5.16 Device information is correct - PASS
• 5.17 Links are correct - PASS FAIL
• Links are incorrect
• 5.18 Hosts are correct - PASS FAIL
• Hosts are incorrect

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 -

...

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 FAIL
• ONOS7 hosts don't match Mininet
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS FAIL
• Host information is incorrect
• 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 FAIL
• ONOS shows 2 SCCs
• 8.8 Device information is correct - PASS
• 8.9 Links are correct - PASS FAIL
• Links are incorrect
• 8.10 Hosts are correct - PASS FAIL
• Hosts are incorrect
• 8.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 - 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 -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

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

Case 15: Check that Leadership Election App is still functional - 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 Comparing ONOS topology to MN - No Result
• 8.2 Collecting topology information from ONOS - PASS FAIL
• ONOS7 hosts don't match Mininet
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - FAIL
• Host information is
correct - PASS
• incorrect
• 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 FAIL
• ONOS shows 2 SCCs
• 8.8 Device information is correct - PASS
• 8.9 Links are correct - PASS FAIL
• Links are incorrect
• 8.10 Hosts are correct - PASS FAIL
• Hosts are incorrect
• 8.11 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 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 - PASS FAIL
• Intents have not been installed correctly, pings failed.

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 -

...

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 FAIL
• ONOS7 hosts don't match Mininet
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS FAIL
• Host information is incorrect
• 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 FAIL
• ONOS shows 2 SCCs
• 8.8 Device information is correct - PASS
• 8.9 Links are correct - PASS FAIL
• Links are incorrect
• 8.10 Hosts are correct - PASS FAIL
• Hosts are incorrect
• 8.11 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 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 - 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

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN - No Result
• 8.2 Collecting topology information from ONOS - PASS FAIL
• ONOS7 hosts don't match Mininet
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS FAIL
• Host information is incorrect
• 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 FAIL
• ONOS shows 2 SCCs
• 8.8 Device information is correct - PASS
• 8.9 Links are correct - PASS FAIL
• Links are incorrect
• 8.10 Hosts are correct - PASS FAIL
• Hosts are incorrect
• 8.11 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 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 - PASS 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 Comparing ONOS topology to MN - No Result
• 8.2 Collecting topology information from ONOS - PASS FAIL
• ONOS7 hosts don't match Mininet
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - FAIL
• Host information is
correct - PASS
• incorrect
• 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 FAIL
• ONOS shows 2 SCCs
• 8.8 Device information is correct - PASS
• 8.9 Links are correct - PASS FAIL
• Links are incorrect
• 8.10 Hosts are correct - PASS FAIL
• Hosts are incorrect
• 8.11 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 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 - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

...