Page History

...

commit 878868aaf8ad97f9f19e3ac92fcb981943a89a5d 3c9e8c377b62353199682f620558ed93ec94e7aa (HEAD, origin/onos-1.10, onos-1.10)
Author: Jonathan Hart Ray Milkey [jono@opennetworkingray@opennetworking.org]
AuthorDate: Wed Aug 16 16:46:36 Thu Sep 28 19:39:12 2017 -0700
Commit: Jonathan Hart Ray Milkey [jono@opennetworkingray@opennetworking.org]
CommitDate: Wed Aug 16 16:46:36 Thu Sep 28 19:39:12 2017 -0700
Rename route REST API to routes to match others
Starting snapshot 1.10.8-SNAPSHOT

<iframe src="https://onos-jenkins.onlab.us/job/HAsanity/plot/Plot-HA/getPlot?index=2&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

Set up ONOS with 7 node(s) ONOS cluster

• 1.1 Constructing test variables - PASS
• 1.2 Apply Applying cell variable to environment - PASS No Result
• 1.3 Uninstalling ONOS package Starting Mininet - PASS
• 1.4 Starting Mininet - PASS Git checkout and pull master - No Result
• 1.5 Creating ONOS package - PASS
• 1.6 Installing ONOS package - PASS
• 1.7 Set up ONOS secure SSH - PASS
• 1.8 Checking ONOS service if ONOS is up yet - 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 Check app ids App Ids check - PASS

Case 2: Assigning devices to controllers - PASS

...

• 5.1 Check that each switch has a master - PASS
• 5.2 Get the Mastership of each switch from each controller - No Result 5.3 Read device roles from ONOS - PASS
• 5.4 3 Check for consistency in roles from each controller - PASS
• 5.5 4 Get the intents from each controller - PASS
• 5.6 5 Check for consistency in Intents from each controller - PASS
• 5.7 6 Get the flows from each controller - PASS
• 5.8 7 Check for consistency in Flows from each controller - PASS
• 5.9 8 Get the OF Table entries - No Result
• 5.10 9 Start continuous pings - No Result
• 5.11 10 Collecting topology information from ONOS - No Result
• 5.12 11 Host view is consistent across ONOS nodes - PASS
• 5.13 12 Each host has an IP address - PASS
• 5.14 13 Cluster view is consistent across ONOS nodes - PASS
• 5.15 14 Cluster view correct across ONOS nodes - PASS
• 5.16 15 Comparing ONOS topology to MN - PASS
• 5.17 16 Device information is correct - PASS
• 5.18 17 Links are correct - PASS
• 5.19 18 Hosts are correct - PASS

Case 14: Start Leadership Election app - 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 Compare switch roles from before failure - PASS
• 7.5 Get the intents from each controller and compare across all nodes - PASS
• 7.6 Check for consistency in Intents from each controller - PASS
• 7.7 Compare current intents with intents before the failure - PASS
• 7.8 Get the OF Table entries and compare to before component failure - PASS
• 7.9 Leadership Election is still functional - PASS

...