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.
...
05
commit 6584989c59151a1f84eaee250116ac83ebeb305e 0c2841c4b22e8adeb85692877417b319fb7f42ea (HEAD, origin/master, origin/HEAD, masteronos-1.11, onos-1.11)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.comYi Tseng [yi@opennetworking.org]
AuthorDate: Fri Tue Aug 18 1315 10:0954:41 14 2017 -0700
Commit: Ray Milkey [ray@opennetworking.org]
CommitDate: Sat Mon Aug 19 0221 20:5205:33 05 2017 +0000
minor fixes around HexString
[ONOS-6916] Fix bmv2 flow programmable and PiCriterionTranslator
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>
|
...
Case 5: Setting up and gathering data for current state - PASS
...
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch from each controller - No Result
- 5.3 Read device roles from ONOS - PASS
- 5.4 Check for consistency in roles from each controller - PASS
- 5.5 Get the intents from each controller - PASS
- 5.6 Check for consistency in Intents from each controller - PASS
- 5.7 Get the flows from each controller - PASS
- 5.8 Check for consistency in Flows from each controller - PASS
- 5.9 Get the OF Table entries - No Result
- 5.10 Start continuous pings - No Result
- 5.11 Collecting topology information from ONOS - No Result
- 5.12 Host view is consistent across ONOS nodes - PASS
- 5.13 Each host has an IP address - PASS
- 5.14 Cluster view is consistent across ONOS nodes - PASS
- 5.15 Cluster view correct across ONOS nodes - PASS
- 5.16 Comparing ONOS topology to MN - PASS
- 5.17 Device information is correct - PASS
- 5.18 Links are correct - PASS
- 5.19 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 6: Restart entire ONOS cluster - PASS
- 6.1 Checking ONOS Logs for errors - No Result
- 6.2 Checking ONOS service - PASS
- 6.3 Starting ONOS CLI sessions - 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 from each controller - PASS
- 7.5 Check for consistency in Intents from each controller - PASS
- 7.6 Leadership Election is still functional - 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 9: Turn off a link to ensure that Link Discovery is working properly - PASS
- 9.1 Kill Link between s3 and s28 - 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 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 - PASS
...
- 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 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 - FAIL Intents are not all in INSTALLED 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 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 - PASS
...
- 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 4: Verify connectivity by sending traffic across Intents - PASS
Ping across added host intents to check functionality and check the state of the intent
...
Case 13: Test Cleanup - PASS
...
- 13.1 Killing tcpdumps - No Result
- 13.2 Stopping Mininet - PASS
- 13.3 Checking ONOS Logs for errors - No Result