Page History

HATestClusterRestart at 11 30 Jun 2015 0203:5901:4049

commit fff38a6bec95e58f6b57f3ba9874d5021414ca43 fdba99862c594dca7672eb09fea8584a3dd99a87 (HEAD, origin/onos-1.2, onos-1.2)
Author: Brian O'Connor [bocon@onlab.usalshabib [alshabibi.ali@gmail.com]
AuthorDate: Fri Jun 5 2326 13:4820:18 54 2015 -0700
Commit: Brian O'Connor [bocon@onlab.usalshabib [alshabibi.ali@gmail.com]
CommitDate: Fri Jun 5 2326 15:4843:18 59 2015 -0700
Manually bumping cord-gui version to
adding a dockerfile for onos-1.2.1

Case 1: Setting up test environment - PASS

...

• 1.1 Applying cell variable to environment - No Result Result 
• 1.2 Starting Mininet - PASS PASS 
• 1.3 Git checkout and pull master - No Result Result 
• 1.4 Using mvn clean install - PASS PASS 
• 1.5 Creating ONOS package - PASS PASS 
• 1.6 Installing ONOS package - PASS PASS 
• 1.7 Checking if ONOS is up yet - PASS PASS 
• 1.8 App Ids check - PASS PASS 

Case 2: Assigning devices to controllers - PASS

...

• 2.1 Assign switches to controllers - PASS PASS 

Case 8: Compare ONOS Topology view to Mininet topology - PASS

...

• 8.1 Create TestONTopology object - PASS PASS 
• 8.2 Comparing ONOS topology to MN - No Result Result 
• 8.3 Collecting topology information from ONOS - PASS PASS 
• 8.4 Hosts view is consistent across all ONOS nodes - PASS PASS 
• 8.5 Hosts information is correct - PASS PASS 
• 8.6 Host attachment points to the network - PASS PASS 
• 8.7 Clusters view is consistent across all ONOS nodes - PASS PASS 
• 8.8 There is only one SCC - PASS PASS 
• 8.9 Device information is correct - PASS PASS 
• 8.10 Port information is correct - PASS PASS 
• 8.11 Links are correct - PASS PASS 
• 8.12 Checking ONOS nodes - PASS PASS 

Case 3: Adding host Intents - PASS

...

• 3.1 Install reactive forwarding app - PASS PASS 
• 3.2 Check app ids - PASS PASS 
• 3.3 Discovering Hosts( Via pingall for now ) - PASS PASS 
• 3.4 Uninstall reactive forwarding app - PASS PASS 
• 3.5 Check app ids - PASS PASS 
• 3.6 Add host intents via cli - PASS PASS 
• 3.7 Intent Anti-Entropy dispersion - PASS PASS 

Case 8: Compare ONOS Topology view to Mininet topology - PASS

...

• 8.1 Create TestONTopology object - PASS PASS 
• 8.2 Comparing ONOS topology to MN - No Result Result 
• 8.3 Collecting topology information from ONOS - PASS PASS 
• 8.4 Hosts view is consistent across all ONOS nodes - PASS PASS 
• 8.5 Hosts information is correct - PASS PASS 
• 8.6 Host attachment points to the network - PASS PASS 
• 8.7 Clusters view is consistent across all ONOS nodes - PASS PASS 
• 8.8 There is only one SCC - PASS PASS 
• 8.9 Device information is correct - PASS PASS 
• 8.10 Port information is correct - PASS PASS 
• 8.11 Links are correct - PASS PASS 
• 8.12 Checking ONOS nodes - PASS PASS 

Case 4: Verify connectivity by sendind traffic across Intents - PASS

...

• 4.1 Ping across added host intents - PASS PASS 
• 4.2 Check Intent state - PASS PASS 
• 4.3 Check leadership of topics - PASS PASS 
• 4.4 Wait a minute then ping again - PASS PASS 

Case 5: Setting up and gathering data for current state - PASS

...

• 5.1 Check that each switch has a master - PASS PASS 
• 5.2 Get the Mastership of each switch from each controller - PASS PASS 
• 5.3 Check for consistency in roles from each controller - PASS PASS 
• 5.4 Get the intents from each controller - PASS PASS 
• 5.5 Check for consistency in Intents from each controller - PASS PASS 
• 5.6 Get the flows from each controller - PASS PASS 
• 5.7 Check for consistency in Flows from each controller - PASS PASS 
• 5.8 Get the OF Table entries - No Result Result 
• 5.9 Start continuous pings - No Result Result 
• 5.10 Create TestONTopology object - No Result Result 
• 5.11 Collecting topology information from ONOS - No Result Result 
• 5.12 Host view is consistent across ONOS nodes - PASS PASS 
• 5.13 Each host has an IP address - PASS PASS 
• 5.14 Cluster view is consistent across ONOS nodes - PASS PASS 
• 5.15 Cluster view correct across ONOS nodes - PASS PASS 
• 5.16 Comparing ONOS topology to MN - PASS PASS 

Case 14: Start Leadership Election app - PASS

...

• 14.1 Install leadership election app - PASS PASS 
• 14.2 Run for election on each node - PASS PASS 
• 14.3 Check that each node shows the same leader - PASS PASS 

Case 16: Install Primitives app - PASS

...

• 16.1 Install Primitives app - PASS PASS 

Case 17: Check for basic functionality with distributed primitives - PASS

...

• 17.1 Increment and get a default counter on each node - PASS PASS 
• 17.2 Increment and get an in memory counter on each node - PASS PASS 
• 17.3 Check counters are consistant across nodes - PASS PASS 
• 17.4 Counters we added have the correct values - PASS PASS 
• 17.5 Distributed Set get - PASS PASS 
• 17.6 Distributed Set size - PASS PASS 
• 17.7 Distributed Set add() - PASS PASS 
• 17.8 Distributed Set addAll() - PASS PASS 
• 17.9 Distributed Set contains() - PASS PASS 
• 17.10 Distributed Set containsAll() - PASS PASS 
• 17.11 Distributed Set remove() - PASS PASS 
• 17.12 Distributed Set removeAll() - PASS PASS 
• 17.13 Distributed Set addAll() - PASS PASS 
• 17.14 Distributed Set clear() - PASS PASS 
• 17.15 Distributed Set addAll() - PASS PASS 
• 17.16 Distributed Set retain() - PASS PASS 

Case 6: Restart entire ONOS cluster - PASS

• 6.1 Killing ONOS nodes - PASS PASS 
• 6.2 Checking if ONOS is up yet - PASS PASS 

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

...

• 8.1 Create TestONTopology object - PASS PASS 
• 8.2 Comparing ONOS topology to MN - No Result Result 
• 8.3 Collecting topology information from ONOS - PASS PASS 
• 8.4 Hosts view is consistent across all ONOS nodes - PASS PASS 
• 8.5 Hosts information is correct - PASS PASS 
• 8.6 Host attachment points to the network - FAIL FAIL 
• ONOS did not correctly attach hosts to the network
• 8.7 Clusters view is consistent across all ONOS nodes - PASS PASS 
• 8.8 There is only one SCC - PASS PASS 
• 8.9 Device information is correct - PASS PASS 
• 8.10 Port information is correct - PASS PASS 
• 8.11 Links are correct - PASS PASS 
• 8.12 Checking ONOS nodes - PASS 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 PASS 
• 3.2 Check app ids - PASS PASS 
• 3.3 Discovering Hosts( Via pingall for now ) - PASS FAIL 
• Reactive Pingall failed, one or more ping pairs failed
• 3.4 Uninstall reactive forwarding app - PASS PASS 
• 3.5 Check app ids - PASS PASS 
• 3.6 Add host intents via cli - PASS PASS 
• 3.7 Intent Anti-Entropy dispersion - PASS PASS 

Case 7: Running ONOS Constant State Tests -

...

FAIL

• 7.1 Check that each switch has a master - PASS PASS 
• 7.2 Read device roles from ONOS - PASS PASS 
• 7.3 Check for consistency in roles from each controller - PASS PASS 
• 7.4 Get the intents and compare across all nodes - PASS PASS 
• 7.5 Check for consistency in Intents from each controller - PASS PASS 
• 7.6 Get the OF Table entries and compare to before component failure - PASS FAIL 
• Changes were found in the flow tables
• 7.7 Leadership Election is still functional - PASS 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 PASS 
• 4.3 Check leadership of topics - PASS PASS 
• 4.4 Wait a minute then ping again - PASS .4 Wait a minute then ping again - FAIL 
• Intents have not been installed correctly, pings failed.

Case 15: Check that Leadership Election is still functional - PASS

...

• 15.1 Run for election on each node - PASS PASS 
• 15.2 Check that each node shows the same leader - PASS PASS 
• 15.3 Find current leader and withdraw - PASS PASS 
• 15.4 Make sure new leader is elected - PASS PASS 
• 15.5 Run for election on old leader( just so everyone is in the hat ) - PASS PASS 
• 15.6 Leader did not change when old leader re-ran - PASS PASS 

Case 17: Check for basic functionality with distributed primitives - PASS

...

• 17.1 Increment and get a default counter on each node - PASS PASS 
• 17.2 Increment and get an in memory counter on each node - PASS PASS 
• 17.3 Check counters are consistant across nodes - PASS PASS 
• 17.4 Counters we added have the correct values - PASS PASS 
• 17.5 Distributed Set get - PASS PASS 
• 17.6 Distributed Set size - PASS PASS 
• 17.7 Distributed Set add() - PASS PASS 
• 17.8 Distributed Set addAll() - PASS PASS 
• 17.9 Distributed Set contains() - PASS PASS 
• 17.10 Distributed Set containsAll() - PASS PASS 
• 17.11 Distributed Set remove() - PASS PASS 
• 17.12 Distributed Set removeAll() - PASS PASS 
• 17.13 Distributed Set addAll() - PASS PASS 
• 17.14 Distributed Set clear() - PASS PASS 
• 17.15 Distributed Set addAll() - PASS PASS 
• 17.16 Distributed Set retain() - PASS PASS 

Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS

...

• 9.1 Kill Link between s3 and s28 - PASS PASS 

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS PASS 
• 8.2 Comparing ONOS topology to MN - No Result Result 
• 8.3 Collecting topology information from ONOS - PASS PASS 
• 8.4 Hosts view is consistent across all ONOS nodes - PASS PASS 
• 8.5 Hosts information is correct - PASS PASS 
• 8.6 Host attachment points to the network - PASS FAIL 
• ONOS did not correctly attach hosts to the network
• 8.7 Clusters view is consistent across all ONOS nodes - PASS PASS 
• 8.8 There is only one SCC - PASS PASS 
• 8.9 Device information is correct - PASS PASS 
• 8.10 Port information is correct - PASS PASS 
• 8.11 Links are correct - PASS PASS 
• 8.12 Checking ONOS nodes - PASS 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 - FAIL 
• Intents have not been installed correctly, pings failed.
4.1 Ping across added host intents - PASS
• 4.2 Check Intent state - PASS PASS 
• 4.3 Check leadership of topics - PASS 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 PASS 

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS PASS 
• 8.2 Comparing ONOS topology to MN - No Result Result 
• 8.3 Collecting topology information from ONOS - PASS PASS 
• 8.4 Hosts view is consistent across all ONOS nodes - PASS PASS 
• 8.5 Hosts information is correct - PASS PASS 
• 8.6 Host attachment points .6 Host attachment points to the network - FAIL 
• ONOS did not correctly attach hosts to the network
- PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS PASS 
• 8.8 There is only one SCC - PASS PASS 
• 8.9 Device information is correct - PASS PASS 
• 8.10 Port information is correct - PASS PASS 
• 8.11 Links are correct - PASS PASS 
• 8.12 Checking ONOS nodes - PASS 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 PASS 
• 4.3 Check leadership of topics - PASS 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 PASS 

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS PASS 
• 8.2 Comparing ONOS topology to MN - No Result Result 
• 8.3 Collecting topology information from ONOS - PASS PASS 
• 8.4 Hosts view is consistent across all ONOS nodes - PASS PASS 
• 8.5 Hosts information is correct - PASS PASS 
• 8.6 Host attachment points to the network - PASS FAIL 
• ONOS did not correctly attach hosts to the network
• 8.7 Clusters view is consistent across all ONOS nodes - PASS PASS 
• 8.8 There is only one SCC - PASS PASS 
• 8.9 Device information is correct - PASS PASS 
• 8.10 Port information is correct - PASS PASS 
• 8.11 Links are correct - PASS PASS 
• 8.12 Checking ONOS nodes - PASS 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 PASS 
• 4.3 Check leadership of topics - PASS 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 -

...

FAIL

• 12.1 Add back s5 - PASS FAIL 
• Failed to add switch?

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS PASS 
• 8.2 Comparing ONOS topology to MN - No Result Result 
• 8.3 Collecting topology information from ONOS - PASS PASS 
• 8.4 Hosts view is consistent across all ONOS nodes - PASS PASS 
• 8.5 Hosts information is correct - PASS PASS 
• 8.6 Host attachment points to the network - PASS FAIL 
• ONOS did not correctly attach hosts to the network
• 8.7 Clusters view is consistent across all ONOS nodes - PASS PASS 
• 8.8 There is only one SCC - PASS PASS 
• 8.9 Device information is correct - PASS PASS 
• 8.10 Port information is correct - PASS PASS 
• 8.11 Links are correct - PASS PASS 
• 8.12 Checking ONOS nodes - PASS 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 PASS 
• 4.3 Check leadership of topics - PASS PASS 
• 4.4 Wait a minute then ping again - PASS FAIL 
• Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

...

• 13.1 Killing tcpdumps - No Result Result 
• 13.2 Copying MN pcap and ONOS log files to test station - No Result Result 
• 13.3 Stopping Mininet - PASS PASS 
• 13.4 Checking ONOS Logs for errors - No Result Result 
• 13.5 Packing and rotating pcap archives - No Result Result