commit bcf1a48e897f02284a7aebfeb104adf03e398a5b (HEAD, origin/master, origin/HEAD, master)
Author: Madan Jampani [madan@onlab.us]
AuthorDate: Wed Jun 24 19:05:56 2015 -0700
Commit: Madan Jampani [madan@onlab.us]
CommitDate: Wed Jun 24 19:35:33 2015 -0700
Removed ClockService[K, V] and replaced its usage with a BiFunction[K, V, Timestamp]
Case 1: Setting up test environment - PASS
Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.
- 1.1 Applying cell variable to environment - No Result
- 1.2 Starting Mininet - PASS
- 1.3 Git checkout and pull master - PASS
- 1.4 Using mvn clean install - PASS
- 1.5 Creating ONOS package - PASS
- 1.6 Installing ONOS package - PASS
- 1.7 Checking if ONOS is up yet - PASS
- 1.8 App Ids check - PASS
Case 2: Assigning devices to controllers - PASS
Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.
- 2.1 Assign switches to controllers - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Collecting topology information from ONOS - PASS
- 8.4 Hosts view is consistent across all ONOS nodes - PASS
- 8.5 Hosts information is correct - PASS
- 8.6 Host attachment points to the network - PASS
- 8.7 Clusters view is consistent across all ONOS nodes - PASS
- 8.8 There is only one SCC - PASS
- 8.9 Device information is correct - PASS
- 8.10 Port information is correct - FAIL
- Port information is incorrect
- 8.11 Links are correct - PASS
- 8.12 Checking ONOS nodes - PASS
Case 21: Assigning Controller roles for switches - FAIL
Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'
- 21.1 Assign mastership of switches to specific controllers - PASS
- 21.2 Check mastership was correctly assigned - FAIL
- Switches were not successfully reassigned
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Create TestONTopology object - PASS
- 8.2 Comparing ONOS topology to MN - No Result
- 8.3 Collecting topology information from ONOS - PASS
- 8.4 Hosts view is consistent across all ONOS nodes - PASS
- 8.5 Hosts information is correct - PASS
- 8.6 Host attachment points to the network - PASS
- 8.7 Clusters view is consistent across all ONOS nodes - PASS
- 8.8 There is only one SCC - PASS
- 8.9 Device information is correct - PASS
- 8.10 Port information is correct - FAIL
- Port information is incorrect
- 8.11 Links are correct - PASS
- 8.12 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 - FAIL
- Intent ECM anti-entropy took too long
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.2 Check Intent state - PASS
- 4.3 Check leadership of topics - FAIL
- Some topics were lost
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 5: Setting up and gathering data for current state - FAIL
- 5.1 Check that each switch has a master - FAIL
- Some devices don't have a master assigned
- 5.2 Get the Mastership of each switch from each controller - PASS
- 5.3 Check for consistency in roles from each controller - 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 Create TestONTopology object - No Result
- 5.11 Collecting topology information from ONOS - No Result
- 5.12 Host view is consistent across ONOS nodes - PASS
- 5.13 Each host has an IP address - PASS
- 5.14 Cluster view is consistent across ONOS nodes - PASS
- 5.15 Cluster view correct across ONOS nodes - FAIL
- ONOS shows 14 SCCs
- 5.16 Comparing ONOS topology to MN - FAIL
- Topology Check Test NOT successful
Case 14: Start Leadership Election app - FAIL
- 14.1 Install leadership election app - PASS
- 14.2 Run for election on each node - FAIL
- Failed to run for leadership
- 14.3 Check that each node shows the same leader - FAIL
- Nodes have different leaders
Case 16: Install Primitives app - PASS
- 16.1 Install Primitives app - PASS
Case 17: Check for basic functionality with distributed primitives - No Result
- 17.1 Increment and get a default counter on each node - FAIL
- Error incrementing default counter
- 17.2 Increment and get an in memory counter on each node - PASS
- 17.3 Check counters are consistant across nodes - FAIL
- ONOS Counters are inconsistent across nodes