Page History

...

commit d9bbde88b9e280261a9b9269d1944b0252dbc81c 590160aa0f27bc32c246ab72a78019e7be409dec (HEAD, origin/master, origin/HEAD, master)
Author: Ray Milkey Madan Jampani [ray@onlabmadan@onlab.us]
AuthorDate: Thu Tue Jun 9 1114 16:3549:00 44 2016 -0700
Commit: Gerrit Code Review [gerrit@onlabBrian O'Connor [bocon@onlab.us]
CommitDate: Fri Wed Jun 10 2015 05:2637:36 13 2016 +0000
Fix ONOS-4683 - Don't process device events on the listener thread
Ensure cluster metadata is setup as part of onos-run-karaf

<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=1&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 - 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 - PASS
• 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 - No Result

• 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 - FAIL
• ONOS nodes have different views of hosts
• 8.3 Hosts information is correct - FAIL
• Host information is incorrect
• 8.4 Host attachment points to the network - PASS