1.3-HA Sanity

commit 6f3f79f7f5edc4f6b0e79ccb1a6f3d8cf9c25e35 (HEAD, origin/onos-1.2, onos-1.2)
Author: Jon Hall [jhall@onlab.us]
AuthorDate: Tue Aug 25 16:22:41 2015 -0700
Commit: Brian O'Connor [bocon@onlab.us]
CommitDate: Thu Sep 3 19:11:53 2015 +0000

ONOS-2801
--
(cherry picked from commit df6a6e4af8eb704529b985e4a9f9b7edbb337703)

Case 1: Setting up test environment - PASS

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 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 - 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 - FAIL
• ONOS shows 0 SCCs
• 8.8 Device information is correct - FAIL
• Device information is incorrect
• 8.9 Links are correct - FAIL
• Links are incorrect
• 8.10 Hosts are correct - PASS
• 8.11 Checking ONOS nodes - PASS

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 - 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 - FAIL
• ONOS shows 0 SCCs
• 8.8 Device information is correct - FAIL
• Device information is incorrect
• 8.9 Links are correct - FAIL
• Links are incorrect
• 8.10 Hosts are correct - PASS
• 8.11 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 ) - FAIL
• Reactive Pingall failed, one or more ping pairs failed
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - PASS
• 3.6 Add host intents via cli - FAIL
• Error looking up host ids
• 3.7 Intent Anti-Entropy dispersion - 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.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.