Page History

...

commit 06613e9e35fa37b83c87ef7f03ca8923752b83dc 8f057ee431ebadeec8da510362f66eb94b2a9e4e (HEAD, origin/master, origin/HEAD, master)
Author: Sean Condon Simon Hunt [seansimon@onlab.condon@microsemi.comus]
AuthorDate: Fri Jun 9 15:14:01 2017 +0100Wed Jul 19 14:05:26 2017 -0700
Commit: Sean Condon Simon Hunt [seansimon@opennetworking.condon@microsemi.comorg]
CommitDate: Mon Thu Jul 17 2120 02:4025:31 07 2017 +0100
Updating Microsemi Driver to onos-yang-tools 2.x0000

ONOS-6334: Flow treatments immediate vs deferred, should be clearer.

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

Case 1:

...

Starting up 7 node(s) ONOS cluster - PASS

Set up ONOS with 7 node(s) ONOS cluster

• 1.1 Constructing test variables - PASS

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

• 1.1 Create cell file - No Result
• 1.2 Applying Apply cell variable to environment - No Result PASS
• 1.3 Starting Mininet Uninstalling ONOS package - PASS
• 1.4 Git checkout and pull master - No Result Starting Mininet - PASS
• 1.5 Creating ONOS package - PASS
• 1.6 Installing ONOS package - PASS
• 1.7 Set up ONOS secure SSH - PASS
• 1.8 Checking if ONOS is up yet Starting ONOS service - PASS
• 1.9 Starting ONOS CLI sessions - PASS
• 1.10 Checking ONOS nodes - PASS
• 1.11 Activate apps defined in the params file - No Result
• 1.12 Set ONOS configurations - PASS
• 1.13 App Ids check - PASS

...

• 7.1 Check that each switch has a master - PASS
• 7.2 Read device roles from ONOS - PASS
• 7.3 Check for consistency in roles from each controller - PASS
• 7.4 Get the intents and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller - PASS
• 7.6 Compare current intents with intents before the failure - PASS FAIL
• The Intents changed during failure
• 7.7 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• 7.8 Leadership Election is still functional - 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 - PASS FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 15: Check that Leadership Election is still functional - PASS

...