commit 5e1f42d8ebc6dfa1ed0347d750fb9a6562addbf2 (HEAD, tag: 1.6.0-rc3)
Author: Thomas Vachuska [tom@onlab.us]
AuthorDate: Thu Jun 16 20:07:09 2016 -0700
Commit: Thomas Vachuska [tom@onlab.us]
CommitDate: Thu Jun 16 20:07:09 2016 -0700

Tagging 1.6.0-rc3

<iframe src="https://onos-jenkins.onlab.us/job/HAswapNodes/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

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 Checking if ONOS is up yet - PASS
• 1.13 Checking ONOS nodes - PASS
• 1.14 Activate apps defined in the params file - No Result
• 1.15 Set ONOS configurations - PASS
• 1.16 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 - FAIL
• ONOS topology don't match Mininet
• 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 - FAIL
• ONOS shows 27 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
• Links are incorrect
• 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