HAsanity at 20 Apr 2016 11:21:43
commit ec9f595a2d51d892fe301b5378a39c51a0c0e942 (HEAD, origin/onos-1.5, onos-1.5)
Author: Madan Jampani [madan@onlab.us]
AuthorDate: Thu Apr 7 20:16:16 2016 -0700
Commit: Madan Jampani [madan@onlab.us]
CommitDate: Tue Apr 19 09:18:12 2016 -0700
Turning adaptive flow sampling off by default
<iframe src="https://onos-jenkins.onlab.us/job/HAsanity/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>
|
Case 1: Setting up test environment - FAIL
Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.
- 1.1 Create cell file - No Result
- 1.2 Applying cell variable to environment - No Result
- 1.3 Starting Mininet - PASS
- 1.4 Git checkout and pull master - No Result
- 1.5 Using mvn clean install - PASS
- 1.6 Creating ONOS package - PASS
- 1.7 Installing ONOS package - PASS
- 1.8 Checking if ONOS is up yet - PASS
- 1.9 Checking ONOS nodes - FAIL
- Nodes check NOT successful
- 1.10 Activate apps defined in the params file - No Result
- 1.11 Set ONOS configurations - PASS
- 1.12 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 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 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - FAIL
- Nodes check NOT successful
Case 21: Assigning Controller roles for switches - PASS
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 - 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 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 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - FAIL
- Nodes check NOT successful
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
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 Check Intent state - PASS
- 4.2 Ping across added host intents - 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 - FAIL
- 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 - PASS
- 5.4 Get the intents from each controller - PASS
- 5.5 Check for consistency in Intents from each controller - FAIL
- ONOS nodes have different views of intents
- 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
Case 14: Start Leadership Election app - PASS
- 14.1 Install leadership election app - PASS
- 14.2 Run for election on each node - PASS
- 14.3 First node was elected leader - PASS
Case 16: Install Primitives app - PASS
- 16.1 Install Primitives app - PASS