...
commit 99252f0dad5746e7b0f38f1aa234e95af1a3004a 37050d98011571acd44f50b805b304dd0decdcda (HEAD, origin/onos-1.5, onos-1.5)
Author: Brian O'Connor [bocon@onlab.usPhaneendra Manda [phaneendra.manda@huawei.com]
AuthorDate: Fri Mon Mar 11 0214 21:3115:27 56 2016 -0800+0530
Commit: Brian O'Connor [bocon@onlab.usPhaneendra Manda [phaneendra.manda@huawei.com]
CommitDate: Fri Mon Mar 11 0214 21:3115:27 56 2016 -0800
Updating Dockerfile for onos-1.5+0530
[ONOS-4172] Issue fixed to process specific packets in SFC manager
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> |
...
- 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 2 3 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 - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 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 - FAIL
- Intents have not been installed correctly, pings failed.
...
- 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 - FAIL
- PASS
- 8.3 Hosts information is correct - FAIL
- PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 2 SCCs
- PASS
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - 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 and compare across all nodes - PASS
- 7.5 Check for consistency in Intents from each controller - PASS
FAIL
- ONOS nodes have different views of intents
- 7.6 Compare current intents with intents before the failure - PASS
FAIL
- The Intents changed during failure
- 7.7 Get the OF Table entries and compare to before component failure - FAIL
- Changes were found in the flow tables
- 7.8 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 Ping across added host intents - PASS
intents - FAIL
- Intents have not been installed correctly, pings failed.
- 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
...
- 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
FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 2 SCCs
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 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 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS
.2 Check Intent state - FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
...
- 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
FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 2 SCCs
- PASS
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 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 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 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 - FAIL
- Intents have not been installed correctly, pings failed.
...
- 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
FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- PASS
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 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 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 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 - FAIL
- Intents have not been installed correctly, pings failed.
...
- 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
FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 2 SCCs
- PASS
- 8.7 Device information is correct - PASS
FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 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 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 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 - FAIL
- Intents have not been installed correctly, pings failed.
...