...
commit 0d94f06bdfd297f397eaf8694529c604d5892fbc 4f74da03251c670a5317994fa012a835a181c6a4 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlabBrian O'Connor [bocon@onlab.us]
AuthorDate: Thu Jun 4 1015:5634:03 28 2015 -0700
Commit: Simon Hunt [simon@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Fri Jun 4 105 00:5611:10 24 2015 -0700
CORD GUI - include icon_id in user array.+0000
Updating openflowj (0.4.0.onos) and removing snapshot repo
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAClusterRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 16.1 Install Primitives app - PASS
Case 17: Check for basic functionality with distributed primitives - PASS
Test the methods of the distributed primitives (counters and sets) throught the cli
- 17.1 Increment and get a default counter on each node - PASS
- 17.2 Increment and get an in memory counter on each node - PASS
- 17.3 Check counters are consistant across nodes - PASS
- 17.4 Counters we added have the correct values - PASS
- 17.5 Distributed Set get - PASS
- 17.6 Distributed Set size - PASS
- 17.7 Distributed Set add() - PASS
- 17.8 Distributed Set addAll() - PASS
- 17.9 Distributed Set contains() - PASS
- 17.10 Distributed Set containsAll() - PASS
- 17.11 Distributed Set remove() - PASS
- 17.12 Distributed Set removeAll() - PASS
- 17.13 Distributed Set addAll() - PASS
- 17.14 Distributed Set clear() - PASS
- 17.15 Distributed Set addAll() - PASS
- 17.16 Distributed Set retain() - PASS
Case 6: Restart entire ONOS cluster - PASS
- 6.1 Start Packet Capture MN - No Result
- 6.2 Killing ONOS nodes - PASS
- 6.3 Checking if ONOS is up yet - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.4 Checking ONOS nodes - PASS
Case 3: Adding host Intents - PASS
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
Case 7: Running ONOS Constant State Tests - 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 Get the intents and compare across all nodes - PASS
- 7.5 Check for consistency in Intents from each controller - PASS
- 7.6 Get the OF Table entries and compare to before component failure - PASS
- 7.7 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 - PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 15: Check that Leadership Election is still functional - PASS
- 15.1 Run for election on each node - PASS
- 15.2 Check that each node shows the same leader - PASS
- 15.3 Find current leader and withdraw - PASS
- 15.4 Make sure new leader is elected - PASS
- 15.5 Run for election on old leader( just so everyone is in the hat ) - PASS
- 15.6 Leader did not change when old leader re-ran - PASS
Case 17: Check for basic functionality with distributed primitives - PASS
Test the methods of the distributed primitives (counters and sets) throught the cli
- 17.1 Increment and get a default counter on each node - FAIL PASS
- 17.2 Increment and get an in memory counter on each node - FAIL PASS
- 17.3 Check counters are consistant across nodes - PASS
- 17.4 Counters we added have the correct values - PASS
- 17.5 Distributed Set get - PASS
- 17.6 Distributed Set size - PASS
- 17.7 Distributed Set add() - PASS
- 17.8 Distributed Set addAll() - PASS
- 17.9 Distributed Set contains() - PASS
- 17.10 Distributed Set containsAll() - PASS
- 17.11 Distributed Set remove() - PASS
- 17.12 Distributed Set removeAll() - PASS
- 17.13 Distributed Set addAll() - PASS
- 17.14 Distributed Set clear() - PASS
- 17.15 Distributed Set addAll() - PASS
- 17.16 Distributed Set retain() - PASS
Case 9: Turn off a link to ensure that Link Discovery is working properly - 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 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.4 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 - PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
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 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.4 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 - PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
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 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.4 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 - PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - 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 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.4 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 - PASS
- 4.2 Check Intent state - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 13: Test Cleanup - PASS
- 13.1 Killing tcpdumps - No Result
- 13.2 Copying MN pcap and ONOS log files to test station - No Result
- 13.3 Stopping Mininet - PASS
- 13.4 Checking ONOS Logs for errors - No Result
- 13.5 Packing and rotating pcap archives - No Result