...
commit 4e22b2cfa186937b8404282f883909c7cd4069d7 07a572fc947d58aff8f0804b4cee319e7b9f2e25 (HEAD, origin/master, origin/HEAD, master)
Author: Jonathan Hart [jono@onlab.ussangyun-han [sangyun0628@khu.ac.kr]
AuthorDate: Fri Jul 29 1321:3914:15 27 2016 -0700+0900
Commit: Jonathan Hart [jono@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Jul 29 13:39:15 2016 -0700
Add package directories as dependencies of onos-package buck targetWed Aug 3 04:02:12 2016 +0000
[ONOS-4668] Refactoring port statistic collector using SharedExecutor
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAsingleInstanceRestart/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 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 -
...
FAIL
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 FAIL
- Intents have not been installed correctly, pings failed.
- 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 5: Setting up and gathering data for current state - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 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 7: Running ONOS Constant State Tests - PASS
...
- 7.1 Check that each switch has a master - PASS
- 7.2 Check if switch roles are consistent across all nodes - PASS
- 7.3 Compare switch roles from before failure - PASS
- 7.4 Get the intents and compare across all nodes - PASS
- 7.5 Get the OF Table entries and compare to before component failure - PASS
- 7.6 Leadership Election is still functional - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
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 FAIL
- Intents have not been installed correctly, pings failed.
- 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 - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
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 FAIL
- Intents have not been installed correctly, pings failed.
- 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 10: Restore a link to ensure that Link Discovery is working properly - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
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 FAIL
- Intents have not been installed correctly, pings failed.
- 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 11: Killing a switch to ensure it is discovered correctly - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
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 FAIL
- Intents have not been installed correctly, pings failed.
- 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 12: Adding a switch to ensure it is discovered correctly - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents -
...
FAIL
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 FAIL
- Intents have not been installed correctly, pings failed.
- 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 13: Test Cleanup - PASS
...