Page History

...

commit e56d38d2d11a6e0cb040aef9ee8fb1bbbca3d0cf 1a00419e38822df94426d73e1c0904d30a42063d (HEAD, tag: origin/onos-1.6.0-rc5, onos-1.6)
Author: Brian O'Connor [bocon@onlab.usPrince Pereira [prpereir@partner.ciena.com]
AuthorDate: Thu Jun 23 19:06:19 2016 -0700
Commit: Brian O'Connor [bocon@onlabFri Jul 8 16:31:58 2016 +0530
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Jun 23 19:06:50 2016 -0700
Tagging 1.6.0-rc5Fri Jul 8 17:37:40 2016 +0000

cherry picking the fix for ONOS-4754 to onos-1.6 and master

<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 Starting ONOS CLI sessions - FAIL
• ONOS cli startup failed
• PASS
• 1.14 Checking ONOS nodes - PASS
• 1.15 Activate apps defined in the params file - No Result
• 1.16 Set ONOS configurations - FAIL
• Failed to set config
• PASS
• 1.17 App Ids check - FAIL
Something is wrong with app Ids
• PASS

Case 2: Assigning devices to controllers - PASS

...

• 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 - FAIL
• ONOS topology don't match Mininet
• 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 - FAIL
• ONOS nodes have different views of clusters
• PASS
• 8.6 There is only one SCC - FAIL
ONOS shows 27 SCCs
• PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
Links are incorrect
• PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - FAIL
• Nodes check NOT successful
• PASS

Case 21: Assigning Controller roles for switches - PASS

...

• 21.1 Assign mastership of switches to specific controllers - PASS
• 21.2 Check mastership was correctly assigned - 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 - FAIL
• Install fwd failed
• 3.2 Check app ids - FAIL
• Something is wrong with app Ids
• 3.3 Discovering Hosts( Via pingall for now ) - FAIL
• Reactive Pingall failed, one or more ping pairs failed
• 3.4 Uninstall reactive forwarding app - FAIL
• Uninstall fwd failed
• 3.5 Check app ids - FAIL
• Something is wrong with app Ids
• 3.6 Add host intents via cli - FAIL
• Error looking up host ids
• 3.7 Intent Anti-Entropy dispersion - 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 - FAIL
• ONOS nodes have different views of clusters
• 8.6 There is only one SCC - FAIL
• ONOS shows 22 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 - PASS

Case 4: Verify connectivity by sending traffic across Intents - FAIL

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 - FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

Case 5: Setting up and gathering data for current state - No Result

• 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 - PASS
• 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 - FAIL
• ONOS nodes have different views of hosts
• 5.12 Each host has an IP address - PASS