commit d44e0ac9331722b26b3ee7b06c00bfcfa29a3051 (HEAD, origin/master, origin/HEAD, master)
Author: Jonathan Hart [jono@onlab.us]
AuthorDate: Thu Feb 9 16:37:19 2017 -0800
Commit: Simon Hunt [simon@onlab.us]
CommitDate: Fri Feb 10 20:00:48 2017 +0000
Move patchpanel app to onos-app-samples
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 - PASS
- 1.3 Verify connectivity to cell - PASS
- 1.4 Setup server for cluster metadata file - PASS
- 1.5 Generate initial metadata file - PASS
- 1.6 Starting Mininet - PASS
- 1.7 Git checkout and pull master - No Result
- 1.8 Using mvn clean install - PASS
- 1.9 Copying backup config files - PASS
- 1.10 Creating ONOS package - PASS
- 1.11 Installing ONOS package - PASS
- 1.12 Set up ONOS secure SSH - PASS
- 1.13 Checking if ONOS is up yet - PASS
- 1.14 Starting ONOS CLI sessions - PASS
- 1.15 Checking ONOS nodes - PASS
- 1.16 Activate apps defined in the params file - No Result
- 1.17 Set ONOS configurations - PASS
- 1.18 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 - PASS
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 - 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 3: Adding host Intents - PASS
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 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
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 - PASS
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 - No Result
- 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 - FAIL
- Error in reading roles from ONOS
- 5.3 Check for consistency in roles from each controller - FAIL
- ONOS nodes have different views of switch roles
- 5.4 Get the intents from each controller - FAIL
- Error in reading intents from ONOS