Page History

...

commit 9f3158fe802f19a6f372be5956c0abdb0e799fae 1a00419e38822df94426d73e1c0904d30a42063d (HEAD, origin/onos-1.6, onos-1.6)
Author: Madan Jampani [madan@onlab.usPrince Pereira [prpereir@partner.ciena.com]
AuthorDate: Fri Jul 1 108 16:2631:23 58 2016 -0700+0530
Commit: Madan Jampani [madan@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Fri Jul 6 038 17:2037:59 40 2016 +0000
SecurityMode: Ensure store event handling happens in a background thread to avoid deadlocks
--
(cherry picked from commit 67fd1e6233d3b8e4ddb2ed3300c841ed153ba86e)

cherry picking the fix for ONOS-4754 to onos-1.6 and master

<iframe src="https://onos-jenkins.onlab.us/job/HAswapNodes/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 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 - FAIL

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

Compare topology objects between Mininet and ONOS

• 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 24 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - FAIL
• Nodes check NOT successful

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 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
• 5.13 Cluster view is consistent across ONOS nodes - PASS
• 5.14 Cluster view correct across ONOS nodes - FAIL
• ONOS shows 24 SCCs
• 5.15 Comparing ONOS topology to MN - PASS
• 5.16 Device information is correct - PASS
• 5.17 Links are correct - FAIL
• Links are incorrect
• 5.18 Hosts are correct - PASS

Case 14: Start Leadership Election app - FAIL

• 14.1 Install leadership election app - PASS
• 14.2 Run for election on each node - PASS
• 14.3 First node was elected leader - FAIL
• Incorrect leader

Case 16: Install Primitives app - PASS

• 16.1 Install Primitives app - PASS

Case 17: Check for basic functionality with distributed primitives - FAIL

Test the methods of the distributed primitives (counters and sets) throught the cli

• 17.1 Increment then get a default counter on each node - FAIL
• Error incrementing default counter
• 17.2 Get then Increment a default counter on each node - FAIL
• Error incrementing default counter
• 17.3 Counters we added have the correct values - FAIL
• Added counters are incorrect
• 17.4 Add -8 to then get a default counter on each node - FAIL
• Error incrementing default counter
• 17.5 Add 5 to then get a default counter on each node - FAIL
• Error incrementing default counter
• 17.6 Get then add 5 to a default counter on each node - FAIL
• Error incrementing default counter
• 17.7 Counters we added have the correct values - FAIL
• Added counters are incorrect
• 17.8 Distributed Set get - FAIL
• Set elements are incorrect
• 17.9 Distributed Set size - FAIL
• Set sizes are incorrect
• 17.10 Distributed Set add() - FAIL
• Set add was incorrect
• 17.11 Distributed Set addAll() - FAIL
• Set addAll was incorrect
• 17.12 Distributed Set contains() - FAIL
• Set contains failed
• 17.13 Distributed Set containsAll() - PASS
• 17.14 Distributed Set remove() - FAIL
• Set remove was incorrect
• 17.15 Distributed Set removeAll() - FAIL
• Set removeAll was incorrect
• 17.16 Distributed Set addAll() - FAIL
• Set addAll was incorrect
• 17.17 Distributed Set clear() - FAIL
• Set clear was incorrect
• 17.18 Distributed Set addAll() - FAIL
• Set addAll was incorrect
• 17.19 Distributed Set retain() - FAIL
• Set retain was incorrect
• 17.20 Partitioned Transactional maps put - PASS
• 17.21 Partitioned Transactional maps get - FAIL
Partitioned Transactional Map values incorrect