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 c70254e15df6e48bf7f4bc712fdd143f18fd801e 9ab5ec76f306d4fbab0a8f2f4c56f9f8a03cb7b4 (HEAD, origin/onos-1.7, onos-1.7)
Author: Brian O'Connor [bocon@onlab.us]
AuthorDate: Mon Tue Oct 24 25 00:4145:40 00 2016 -0700
Commit: Brian O'Connor [bocon@onlab.us]
CommitDate: Mon Tue Oct 24 1525 07:0150:39 2016 -0700
Moving snmp libs to released version; ejecing bti driver due to incompatibility05 2016 +0000
Updating onos-upload-docs to use Buck build API javadocs
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=1&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 5: Setting up and gathering data for current state -
...
PASS
- 5.1 Check that each switch has a master - FAIL Some devices don't have a master assigned
- PASS
- 5.2 Get the Mastership of each switch from each controller - FAIL
- Error in reading roles from ONOS
- 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 5.3 Check for consistency in roles Flows from each controller - FAIL
- ONOS nodes have different views of switch roles
- 5.4 Get the intents from each controller - FAIL Error in reading intents from ONOS
- - 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 - PASS
- 5.15 Comparing ONOS topology to MN - PASS
- 5.16 Device information is correct - PASS
- 5.17 Links are correct - PASS
- 5.18 Hosts are correct - PASS
Case 14: Start Leadership Election app - PASS
- 14.1 Install leadership election app - PASS
- 14.2 Run for election on each node - PASS
- 14.3 First node was elected leader - PASS
Case 16: Install Primitives app - PASS
- 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 then get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Distributed Set get - PASS
- 17.9 Distributed Set size - PASS
- 17.10 Distributed Set add() - PASS
- 17.11 Distributed Set addAll() - PASS
- 17.12 Distributed Set contains() - PASS
- 17.13 Distributed Set containsAll() - PASS
- 17.14 Distributed Set remove() - PASS
- 17.15 Distributed Set removeAll() - PASS
- 17.16 Distributed Set addAll() - PASS
- 17.17 Distributed Set clear() - PASS
- 17.18 Distributed Set addAll() - PASS
- 17.19 Distributed Set retain() - PASS
- 17.20 Partitioned Transactional maps put - PASS
- 17.21 Partitioned Transactional maps get - PASS
Case 61: Partition ONOS nodes into two distinct partitions - PASS
- 61.1 Checking ONOS Logs for errors - No Result
- 61.2 Partitioning ONOS nodes - PASS
- 61.3 Sleeping 60 seconds - No Result
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 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 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - 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 Compare current intents with intents before the failure - PASS
- 7.7 Get the OF Table entries and compare to before component failure - PASS
- 7.8 Leadership Election is still functional - PASS
Case 4: Verify connectivity by sending traffic across Intents - PASS
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - 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 and candidates - PASS
- 15.3 Find current leader and withdraw - PASS
- 15.4 Check that a new node was elected leader - PASS
- 15.5 Check that that new leader was the candidate of old leader - PASS
- 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
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 then get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Distributed Set get - PASS
- 17.9 Distributed Set size - PASS
- 17.10 Distributed Set add() - PASS
- 17.11 Distributed Set addAll() - PASS
- 17.12 Distributed Set contains() - PASS
- 17.13 Distributed Set containsAll() - PASS
- 17.14 Distributed Set remove() - PASS
- 17.15 Distributed Set removeAll() - PASS
- 17.16 Distributed Set addAll() - PASS
- 17.17 Distributed Set clear() - PASS
- 17.18 Distributed Set addAll() - PASS
- 17.19 Distributed Set retain() - PASS
- 17.20 Partitioned Transactional maps put - PASS
- 17.21 Partitioned Transactional maps get - PASS