Page History

...

...

commit 2a62ef0a9f9dcf21e17c92bd524e635ea4893d98 commit 57a30999a9aeb60574b1ad4fe036c6b4b0002c34 (HEAD, origin/onos-1.5, onos-1.5)
Author: Thomas Vachuska [tom@onlab.usChanghoon Yoon [chyoon87@kaist.ac.kr]
AuthorDate: Mon Mar 28 10:36:30 2016 -0700Wed Jun 29 16:34:38 2016 +0900
Commit: Thomas Vachuska Jonathan Hart [tom@onlabjono@onlab.us]
CommitDate: Mon Mar 28 10:36:30 2016 -0700
Adding ability to push flow rule batches via REST API.Thu Aug 4 00:29:41 2016 +0000

ONOS-4774, ONOS-4775, ONOS-4776 + some minor fixes

<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

• 8.1 Comparing ONOS topology to MN topology - PASS
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS
• 8.9 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

Case 4: Verify connectivity by sending traffic across Intents - PASS

...

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - FAIL
• ONOS shows 4 8 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 7: Running ONOS Constant State Tests -

...

FAIL

• 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 Get the intents and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller - PASS FAIL
• ONOS nodes have different views of intents
• 7.6 Compare current intents with intents before the failure - PASS FAIL
• The Intents changed during failure
• 7.7 Get the OF Table entries and compare to before component failure - PASS FAIL
• Changes were found in the flow tables
• 7.8 Leadership Election is still functional - PASS

...

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

...

• 15.1 Run for election on each node - PASS
• 15.2 Check that each node shows the same leader and candidates - PASS
• 15.3 Find current leader and withdraw - PASS
• 15.4 Check that a new node was elected leader - FAIL
Something went wrong with Leadership election
• PASS
• 15.5 Check that that new leader was the candidate of old leader - FAIL
• Incorrect Candidate Elected
• 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS
• 15.7 Check that oldLeader is a candidate, and leader if only 1 node - PASS

...

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 9 2 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 7: Running ONOS Constant State Tests - FAIL

• 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 Get the intents and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller - FAIL
• ONOS nodes have different views of intents
• 7.6 Compare current intents with intents before the failure - FAIL
• The Intents changed during failure
• 7.7 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• 7.8 Leadership Election is still functional - PASS

...

• 4.1 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 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 is still functional - FAIL

...

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 9 3 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 8 Links are correct - FAIL
• Links are
correct - PASS
• incorrect
• 8.9 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 - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

...

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 9 2 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending 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 FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS again - FAIL
• Intents have not been installed correctly, pings failed.

Case 11: Killing a switch to ensure it is discovered correctly - PASS

...

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 10 2 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending 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 FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - PASS 4.4 Wait a minute then ping again - 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

...

• 8.1 Comparing ONOS topology to MN topology - FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 9 2 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending 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 FAIL
• Intents are not all in INSTALLED state
• 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

...