Page History

...

commit 9ab5ec76f306d4fbab0a8f2f4c56f9f8a03cb7b4 0fc09dc516cc19b3dc524d2aae1393fc9c9bc969 (HEAD, origin/onos-1.7, onos-1.7)
Author: Brian O'Connor [bocon@onlabThomas Vachuska [tom@onlab.us]
AuthorDate: Tue Oct 25 004 11:4550:00 29 2016 -0700
Commit: Brian O'Connor [bocon@onlabThomas Vachuska [tom@onlab.us]
CommitDate: Tue Oct 25 0722:5033:05 07 2016 +0000
Updating
Fixing onos-uploadcreate-docs to use Buck build API javadocsapp to bomb if mvn command fails for some reason.
--
(cherry picked from commit 525651fdc03f8437e3c6fe69d4fb564a78f3e50a)

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

...

Case 8: Compare ONOS Topology view to Mininet topology - PASS

...

• 8.1 Comparing ONOS topology to MN topology - PASS 8.2 Hosts view is consistent across all ONOS nodes - PASS FAIL
• ONOS topology don't match Mininet
• 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 Hosts are correct - PASS
• 8.10 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 - FAIL
• Something is wrong with app Ids
• 3.3 Discovering Hosts( Via pingall for now ) - FAIL
• Reactive Pingall failed, one or more ping pairs failed
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - FAIL
• Something is wrong with app Ids
• 3.6 Add host intents via cli - FAIL
• Error looking up host ids
• 3.7 Intent Anti-Entropy dispersion - FAIL

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 - FAIL
• ONOS nodes have different views of switch roles
• 7.4 Get the intents and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller 2 Hosts view is consistent across all ONOS nodes - FAIL
• ONOS nodes have different views of intentshosts
• 7.6 Compare current intents with intents before the scaling 8.3 Hosts information is correct - FAIL
• The Intents changed during scaling
• 7.7 Get the OF Table entries and compare to before component scaling - FAIL
• Changes were found in the flow tables
• 7.8 Leadership Election is still functional - FAIL
• Something went wrong with Leadership election

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

Case 15: Check that Leadership Election is still functional - FAIL

• Host information is incorrect
• 8.4 Host attachment points to the network - PASS
• 15.1 Run for election on each node - FAIL
• At least one node failed to run for leadership
Skipping the rest of this case.