Page History

...

commit ee1ecd7066a8c91db835d9ed790df5ebef8d369f 3498d1c01d0836c1f87597bc58b14606935e3f53 (HEAD, onos-1.3)
Merge: ab2cf25 8a12779
Author: jenkins [jenkins@onlab.us]
AuthorDate: Tue Sep 15 0921:3300:08 59 2015 -0700
Commit: jenkins [jenkins@onlab.us]
CommitDate: Tue Sep 15 0921:3300:08 59 2015 -0700

<iframe src="https://onos-jenkins.onlab.us/job/HAminorityRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

• 6.1 Killing 3 ONOS nodes - PASS
• 6.2 Checking if ONOS is up yet - PASS
• 6.3 Restarting ONOS main.CLIs - 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
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS
• 8.5 Host attachment points to the network - PASS
• 8.6 Clusters view is consistent across all ONOS nodes - PASS
• 8.7 There is only one SCC - PASS
• 8.8 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 7: Running ONOS Constant State Tests -

...

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
• 7.6 Compare current intents with intents before the failure - PASS
• 7.7 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• PASS
• 7.8 Leadership Election is still functional - FAIL
Something went wrong with Leadership election
• PASS

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 15: Check that Leadership Election is still functional - 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 - PASS
• 15.5 Check that that new leader was the candidate of old leader - PASS
• 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

Case 17: Check for basic functionality with distributed primitives -

...

FAIL

Test the methods of the distributed primitives (counters and sets) throught the cli

• 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
• 17.25 Distributed Set addAll() - PASS
• 17.26 Distributed Set clear() - PASS
• 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 - 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
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS
• 8.5 Host attachment points to the network - PASS
• 8.6 Clusters view is consistent across all ONOS nodes - PASS
• 8.7 There is only one SCC - PASS
• 8.8 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind 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 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 - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 10: Restore a link to ensure that Link Discovery is working properly - 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
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS
• 8.5 Host attachment points to the network - PASS
• 8.6 Clusters view is consistent across all ONOS nodes - PASS
• 8.7 There is only one SCC - PASS
• 8.8 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind 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 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 - PASS FAIL
• Intents have not been installed correctly, pings failed.

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
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS
• 8.5 Host attachment points to the network - PASS
• 8.6 Clusters view is consistent across all ONOS nodes - PASS
• 8.7 There is only one SCC - PASS
• 8.8 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

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

...

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
• 8.3 Hosts view is consistent across all ONOS nodes - PASS
• 8.4 Hosts information is correct - PASS
• 8.5 Host attachment points to the network - PASS
• 8.6 Clusters view is consistent across all ONOS nodes - PASS
• 8.7 There is only one SCC - PASS
• 8.8 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.9 Links are correct - PASS
• 8.10 Checking ONOS nodes - PASS

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

...