...
...
commit 2a62ef0a9f9dcf21e17c92bd524e635ea4893d98 commit dd50f9a798356434140b2cbff26cce22df1cea41 (HEAD, origin/onos-1.5, onos-1.5)
Author: Jayasree Ghosh Changhoon Yoon [jghosh@partnerchyoon87@kaist.cienaac.comkr]
AuthorDate: Thu Wed Jun 9 1829 16:0734:19 38 2016 +05300900
Commit: Gerrit Code Review [gerrit@onlabJonathan Hart [jono@onlab.us]
CommitDate: Fri Jun 10 16:57:38 Thu Aug 4 00:29:41 2016 +0000
ONOS-4635:Fix Issue with add flows using flowobjective-forward REST API with incorrect priority
ONOS-4774, ONOS-4775, ONOS-4776 + some minor fixes
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/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 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 - FAIL
- PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 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
FAIL
Case 4: Verify connectivity by sending traffic across Intents - 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 - FAIL
- 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
...
- 61.1 Checking ONOS Logs for errors - No Result
- 61.2 Partitioning ONOS nodes - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 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 - FAIL
- ONOS shows 4 8 SCCs
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - PASS
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- PASS
- 4.2 Check Intent state - PASS
FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
FAIL
- Intents have not been installed correctly, pings failed.
Case 15: Check that Leadership Election is still functional - FAIL
...
- 62.1 Deleteing firewall rules - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 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 - FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 6 2 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - 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 - FAIL
- Something went wrong with Leadership election
- PASS
- 15.5 Check that that new leader was the candidate of old leader - FAIL
- Incorrect Candidate Elected
- 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 - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 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 - FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 7 3 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - 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 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 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 - FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 6 2 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 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 - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 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 - FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 6 2 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - 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 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 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 - FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 6 2 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - PASS
...