...
commit ccda0b5dc7f62601bbda6d496c5cc96a17f1d315 837e0bb9b082073b94ce152869d06cc829cef12a (HEAD, origin/master, origin/HEAD, master)
Author: Ray Milkey [ray@onlab.usSaurav Das [sauravdas@alumni.stanford.edu]
AuthorDate: Fri Oct 30 1617:5145:06 38 2015 -0700
Commit: Ray Milkey [ray@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Oct 30 17:21:08 2015 -0700
Enable checkstyle rule to enforce package-info.java filesTue Nov 3 01:39:33 2015 +0000
CORD-48 Fixing filtering rule bug in multi-instance operation.
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> |
...
- 2.1 Assign switches to controllers - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - FAIL
- ONOS shows 76 SCCs
- PASS
- 8.8 Device information is correct - FAIL Device information is incorrect
- PASS
- 8.9 Links are correct - PASS
- 8.10 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 - FAIL
- Intent ECM anti-entropy took too long
- PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - FAIL ONOS shows 76 SCCs
- PASS
- 8.8 Device information is correct - FAIL Device information is incorrect
- PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - PASS
...
- 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 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 - 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 76 SCCs
- PASS
- 5.15 Comparing ONOS topology to MN - PASS
- 5.16 Device information is correct - FAIL
- Device information is incorrect
- PASS
- 5.17 Links are correct - PASS
- 5.18 Hosts are correct - PASS
...
- 6.1 Checking ONOS Logs for errors - 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 -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - FAIL
- ONOS shows 76 SCCs
- PASS
- 8.8 Device information is correct - FAIL Device information is incorrect
- PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - 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 - PASS dispersion - FAIL
- Intent ECM anti-entropy took too long
Case 7: Running ONOS Constant State Tests - PASS
...
- 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 -
...
FAIL
- 15.1 Run for election on each node - PASS
- 15.2 Check that each node shows the same leader and candidates - PASS FAIL
- Nodes have different leadersand candidatesand candidatesand candidatesand candidatesand candidatesand candidates
- 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
...
- 9.1 Kill Link between s3 and s28 - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - FAIL
- ONOS shows 76 SCCs
- PASS
- 8.8 Device information is correct - FAIL
- Device information is incorrect
- PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - PASS
...
- 10.1 Bring link between s3 and s28 back up - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - FAIL
- ONOS shows 76 SCCs
- PASS
- 8.8 Device information is correct - FAIL Device information is incorrect
- PASS
- 8.9 Links are correct - PASS
- 8.10 Checking ONOS nodes - 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
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - FAIL ONOS shows 76 SCCs
- PASS
- 8.8 Device information is correct - FAIL Device information is incorrect
- PASS
- 8.9 Links are correct - PASS
- 8.10 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 - FAIL
- Intents have not been installed correctly, pings failed.
- 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 -
...
PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS
- 8.3 Hosts view is consistent across all ONOS nodes - PASS
- 8.4 Hosts information is correct - PASS
- 8.5 Host attachment points to the network - PASS
- 8.6 Clusters view is consistent across all ONOS nodes - PASS
- 8.7 There is only one SCC - FAIL ONOS shows 76 SCCs
- PASS
- 8.8 Device information is correct - FAIL Device information is incorrect
- PASS
- 8.9 Links are correct - PASS
- 8.10 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
...