...
- 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 - 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
FAIL
- Install fwd failed
- 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
...
- 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 - FAIL
- ONOS nodes have different views of switch roles
- 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 - 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
...
- 17.1 Increment then get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Increment and get an in-memory counter on each node - PASS
- 17.9 Get then Increment a in-memory counter on each node - PASS
- 17.10 Counters we added have the correct values - PASS
- 17.11 Add -8 to then get a in-memory counter on each node - PASS
- 17.12 Add 5 to then get a in-memory counter on each node - PASS
- 17.13 Get then add 5 to a in-memory counter on each node - PASS
- 17.14 Counters we added have the correct values - PASS
- 17.15 Check counters are consistant across nodes - PASS
- 17.16 Counters we added have the correct values - PASS
- 17.17 Distributed Set get - PASS
- 17.18 Distributed Set size - PASS
- 17.19 Distributed Set add() - PASS
- 17.20 Distributed Set addAll() - PASS
FAIL
- Set addAll was incorrect
- 17.21 Distributed Set contains() - PASS
- 17.22 Distributed Set containsAll() - PASS
- 17.23 Distributed Set remove() - PASS
- 17.24 Distributed Set removeAll() - PASS
FAIL
- Set removeAll was incorrect
- 17.25 Distributed Set addAll() - PASS
FAIL
- Set addAll was incorrect
- 17.26 Distributed Set clear() - PASS
FAIL
- Set clear was incorrect
- 17.27 Distributed Set addAll() - PASS
FAIL
- Set addAll was incorrect
- 17.28 Distributed Set retain() - PASS
- 17.29 Partitioned Transactional maps put - PASS
- 17.30 Partitioned Transactional maps get - PASS
- 17.31 In-memory Transactional maps put - PASS
- 17.32 In-Memory Transactional maps get - FAIL
- In-Memory Transactional Map values incorrect
...
- 61.1 Checking ONOS Logs for errors - No Result
- 61.2 Partitioning ONOS nodes - 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 - FAIL
- 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 - PASS
- 8.6 There is only one SCC - FAIL
- PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - FAIL
- Links are incorrect
- PASS
- 8.9 Checking ONOS nodes - PASS
Case 7: Running ONOS Constant State Tests -
...
FAIL
- 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 - PASS
FAIL
- Changes were found in the flow tables
- 7.8 Leadership Election is still functional - PASS
...
- 4.1 Ping across added host intents - PASS
FAIL
- Intents have not been installed correctly, pings failed.
- 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 15: Check that Leadership Election is still functional - FAIL
...
- 17.1 Increment then get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Increment and get an in-memory counter on each node - PASS
- 17.9 Get then Increment a in-memory counter on each node - PASS
- 17.10 Counters we added have the correct values - PASS
- 17.11 Add -8 to then get a in-memory counter on each node - PASS
- 17.12 Add 5 to then get a in-memory counter on each node - PASS
- 17.13 Get then add 5 to a in-memory counter on each node - PASS
- 17.14 Counters we added have the correct values - PASS
- 17.15 Check counters are consistant across nodes - PASS
- 17.16 Counters we added have the correct values - PASS
- 17.17 Distributed Set get - PASS
- 17.18 Distributed Set size - PASS
- 17.19 Distributed Set add() - PASS
- 17.20 Distributed Set addAll() - PASS
- 17.21 Distributed Set contains() - PASS
- 17.22 Distributed Set containsAll() - PASS
- 17.23 Distributed Set remove() - PASS
- 17.24 Distributed Set removeAll() - PASS
FAIL
- Set removeAll was incorrect
- 17.25 Distributed Set addAll() - PASS
- 17.26 Distributed Set clear() - PASS
FAIL
- Set clear was incorrect
- 17.27 Distributed Set addAll() - PASS
FAIL
- Set addAll was incorrect
- 17.28 Distributed Set retain() - PASS
- 17.29 Partitioned Transactional maps put - PASS
- 17.30 Partitioned Transactional maps get - PASS
- 17.31 In-memory Transactional maps put - PASS
- 17.32 In-Memory Transactional maps get - FAIL
- In-Memory Transactional Map values incorrect
...
- 62.1 Deleteing firewall rules - 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 - FAIL
- ONOS topology don't match Mininet
- 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 - FAIL
- Device information is incorrect
- PASS
- 8.8 Links are correct - PASS
- 8.9 Checking ONOS nodes - PASS
Case 7: Running ONOS Constant State Tests - FAIL
- 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 - FAIL
- ONOS nodes have different views of intents
- 7.6 Compare current intents with intents before the failure - FAIL
- PASS
- 7.7 Get the OF Table entries and compare to before component failure - FAIL
- PASS
- 7.8 Leadership Election is still functional - PASS
Case 4: Verify connectivity by sending 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
...
- 17.1 Increment then get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Increment and get an in-memory counter on each node - PASS
- 17.9 Get then Increment a in-memory counter on each node - PASS
- 17.10 Counters we added have the correct values - PASS
- 17.11 Add -8 to then get a in-memory counter on each node - PASS
- 17.12 Add 5 to then get a in-memory counter on each node - PASS
- 17.13 Get then add 5 to a in-memory counter on each node - PASS
- 17.14 Counters we added have the correct values - PASS
- 17.15 Check counters are consistant across nodes - PASS
- 17.16 Counters we added have the correct values - PASS
- 17.17 Distributed Set get - PASS
- 17.18 Distributed Set size - PASS
- 17.19 Distributed Set add() - PASS
- 17.20 Distributed Set addAll() - PASS
FAIL
- Set addAll was incorrect
- 17.21 Distributed Set contains() - PASS
- 17.22 Distributed Set containsAll() - PASS
- 17.23 Distributed Set remove() - PASS
- 17.24 Distributed Set removeAll() - PASS
FAIL
- Set removeAll was incorrect
- 17.25 Distributed Set addAll() - PASS
FAIL
- Set addAll was incorrect
- 17.26 Distributed Set clear() - PASS
- 17.27 Distributed Set addAll() - PASS
- 17.28 Distributed Set retain() - PASS
- 17.29 Partitioned Transactional maps put - PASS
- 17.30 Partitioned Transactional maps get - PASS
- 17.31 In-memory Transactional maps put - PASS
- 17.32 In-Memory Transactional maps get - FAIL
- In-Memory Transactional Map values incorrect
...
- 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 topology - FAIL
- 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
- ONOS nodes have different views of clusters
- PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - FAIL
- PASS
- 8.8 Links are correct - PASS
- 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
...
- 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 topology - FAIL
- ONOS topology don't match Mininet
- 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
- ONOS nodes have different views of clusters
- PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- PASS
- 8.8 Links are correct - PASS
- 8.9 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents - PASS
Ping across added host intents to check functionality and check the state of the intent
...
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 topology - FAIL
- 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 - FAIL
- PASS
- 8.8 Links are correct - PASS
- 8.9 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents - PASS
Ping across added host intents to check functionality and check the state of the intent
...
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 topology - FAIL
- ONOS topology don't match Mininet
- 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
- ONOS nodes have different views of clusters
- PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - FAIL
- PASS
- 8.8 Links are correct - PASS
- 8.9 Checking ONOS nodes - PASS
Case 4: Verify connectivity by sending traffic across Intents - PASS
Ping across added host intents to check functionality and check the state of the intent
...