Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
commit 4699b29d6c4415a978609b7a768fa2e71cee221d 66f7543c6b8b65b6b914a648fd184b645a0e42f1 (HEAD, origin/master, origin/HEAD, master)
Author: Ayaka Koshibe Simon Hunt [ayaka@onlabsimon@onlab.us]
AuthorDate: Tue Apr 28 Wed May 6 14:3307:10 03 2015 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed May 6 1821:0020:23 17 2015 +0000
Command for basic testing of LinkResourceService
GUI -- Made OOTB formatters and comparators final classes.
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAClusterRestart/plot/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 8.1 Create TestONTopology object - No Result
- 8.2 Topology view is correct and consistent across all ONOS nodes - PASS
- 8.3 Checking ONOS nodes - PASS
Case 3: Adding host Intents -
...
PASS
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - FAIL PASS
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Check Intent State - No Result 3.8 Intent Anti-Entropy dispersion - PASS
...
- 14.1 Install leadership election app - PASS
- 14.2 Run for election on each node - PASS
- 14.3 Check that each node shows the same leader - PASS
Case 16: Install Primitives app - PASS
...
- 8.1 Create TestONTopology object - No Result
- 8.2 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.3 Checking ONOS nodes - PASS
Case 3: Adding host Intents - FAIL
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - FAIL
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - FAIL
- 3.7 Check Intent State - No Result 3.8 Intent Anti-Entropy dispersion - PASS 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 PASS
- 7.4 Compare switch roles from before failure - FAIL
- 7.5 Get the intents and compare across all nodes - PASS
- 7.6 Check for consistency in Intents from each controller - PASS
- 7.7 Get the OF Table entries and compare to before component failure - FAIL
- 7.8 Check the continuous pings to ensure that no packets were dropped during component failure - FAIL
- 7.9 Leadership Election is still functional - FAIL
Case 4: Ping across added host intents - 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 - FAIL PASS
- 15.2 4 Make sure new leader is elected - FAIL PASS
- 15.3 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 - FAIL
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 - FAIL
- 17.6 Distributed Set size - FAIL
- 17.7 Distributed Set add() - FAIL
- 17.8 Distributed Set addAll() - FAIL
- 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
- 8.1 Create TestONTopology object - No Result
- 8.2 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.3 Checking ONOS nodes - PASS
Case 4: Ping across added host intents - 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 - PASS
- 8.1 Create TestONTopology object - No Result
- 8.2 Topology view is correct and consistent across all ONOS nodes - PASS
- 8.3 Checking ONOS nodes - PASS
Case 4: Ping across added host intents - 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
- 8.1 Create TestONTopology object - No Result
- 8.2 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.3 Checking ONOS nodes - PASS
Case 4: Ping across added host intents - 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
- 8.1 Create TestONTopology object - No Result
- 8.2 Topology view is correct and consistent across all ONOS nodes - FAIL
- 8.3 Checking ONOS nodes - PASS
Case 4: Ping across added host intents - 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