HATestSingleInstanceRestart at 09 Jun 2015 19:36:25

commit 30abc9a1346333b9eb66c063fd1eb9ff2827f23c (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Tue Jun 9 17:13:51 2015 -0700
Commit: Simon Hunt [simon@onlab.us]
CommitDate: Tue Jun 9 17:15:24 2015 -0700

CORD GUI - added CDN to both Basic and Family Bundles, but hide it from GUI display.
<iframe src="https://onos-jenkins.onlab.us/job/HASingleInstanceRestart/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.

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.

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

Case 3: Adding host Intents - PASS

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

Case 4: Verify connectivity by sendind traffic across Intents - PASS

Ping across added host intents to check functionality and check the state of the intent

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

Case 14: Start Leadership Election app - PASS

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

Case 16: Install Primitives app - PASS

Case 17: Check for basic functionality with distributed primitives - FAIL

Test the methods of the distributed primitives (counters and sets) throught the cli

Case 6: Restart ONOS node - PASS

Killing ONOS process and restart cli sessions once onos is up.

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

Case 3: Adding host Intents - PASS

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

Case 7: Running ONOS Constant State Tests - PASS

Case 4: Verify connectivity by sendind traffic across Intents - PASS

Ping across added host intents to check functionality and check the state of the intent

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

Case 17: Check for basic functionality with distributed primitives - FAIL

Test the methods of the distributed primitives (counters and sets) throught the cli

Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

Case 4: Verify connectivity by sendind traffic across Intents - PASS

Ping across added host intents to check functionality and check the state of the intent

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

Case 4: Verify connectivity by sendind traffic across Intents - PASS

Ping across added host intents to check functionality and check the state of the intent

Case 11: Killing a switch to ensure it is discovered correctly - PASS

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

Case 4: Verify connectivity by sendind traffic across Intents - PASS

Ping across added host intents to check functionality and check the state of the intent

Case 12: Adding a switch to ensure it is discovered correctly - PASS

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

Case 4: Verify connectivity by sendind traffic across Intents - PASS

Ping across added host intents to check functionality and check the state of the intent

Case 13: Test Cleanup - PASS