...
commit a88db496d52460c62b54e4e9d688461cbe14afa3 98fc1e7f3f42d7dbcfb49f956743410d2b6269c1 (HEAD, origin/master, origin/HEAD, master)
Author: Sho SHIMIZU [sshimizu@us.fujitsu.com]
AuthorDate: Mon Nov 23 1310:2125:04 22 2015 -0800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Mon Tue Nov 23 2324 02:5756:09 01 2015 +0000
Avoid double wrap of Bandwidth class
Conform to our naming convention for enum
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAsingleInstanceRestart/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 -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
Case 3: Adding host 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 -
...
FAIL
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch - No Result
- 5.3 Get the intents from each controller - No Result
- 5.4 Get the flows from each controller - No Result
- 5.5 Get the OF Table entries - No Result
- 5.6 Collecting topology information from ONOS - No Result
- 5.7 Each host has an IP address - PASS
- 5.8 There is only one dataplane cluster - PASS FAIL
- ONOS shows 2 SCCs
- 5.9 Comparing ONOS topology to MN - PASS
- 5.10 Device information is correct - PASS FAIL
- Device information is incorrect
- 5.11 Links are correct - PASS
- 5.12 Hosts are correct - PASS
...
- 6.1 Checking ONOS Logs for errors - No Result
- 6.2 Killing ONOS processes - PASS
- 6.3 Checking if ONOS is up yet - 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
Case 3: Adding host Intents - 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
Case 4: Verify connectivity by sendind traffic across Intents - 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
Case 4: Verify connectivity by sendind traffic across 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
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
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 - FAIL
- Intents have not been installed correctly, pings failed.
- 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 - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
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 - FAIL Intents have not been installed correctly, pings failed.
- PASS
Case 13: Test Cleanup - PASS
...