Page History

...

commit 97a7033e8873b3a0a6450434167a0601023a29d1 c0fe09a453a8957e60d83e732edb0711950d5065 (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska [tom@onlab.us]
AuthorDate: Wed Thu May 20 0921 12:2956:55 22 2015 -0700
Commit: Thomas Vachuska [tom@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Thu May 21 20 09:2933:55 40 2015 -0700
Fixed onos-package and put hazelcast back into features for now+0000

GUI -- Fixed traffic visualization broken due to change in intent framework.

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

...

Case 6: Restart entire ONOS cluster - PASS

• 6.1 Start Packet Capture MN - No Result
• 6.2 Killing ONOS nodes - PASS
• 6.2 3 Checking if ONOS is up yet - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL PASS
• 8.4 Checking ONOS nodes - PASS

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

• 3.1 Install reactive forwarding app - PASS
• 3.2 Check app ids - PASS
• 3.3 Discovering Hosts( Via pingall for now ) - FAIL PASS
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - PASS
• 3.6 Add host intents via cli - PASS
• 3.7 Intent Anti-Entropy dispersion - 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 Get the OF Table entries and compare to before component failure - FAIL PASS
• 7.7 Check the continuous pings to ensure that no packets were dropped during component failure - FAIL
• 7.8 Leadership Election is still functional - 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

• 4.1 Ping across added host intents - FAIL PASS
• 4.2 Check Intent state - PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL PASS

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

...

• 9.1 Kill Link between s3 and s28 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL PASS
• 8.4 Checking ONOS nodes - 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

• 4.1 Ping across added host intents - FAIL PASS
• 4.2 Check Intent state - PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL PASS

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

...

• 10.1 Bring link between s3 and s28 back up - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL PASS
• 8.4 Checking ONOS nodes - 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

• 4.1 Ping across added host intents - FAIL PASS
• 4.2 Check Intent state - PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL PASS

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

• 11.1 Kill s5 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL PASS
• 8.4 Checking ONOS nodes - 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

• 4.1 Ping across added host intents - FAIL PASS
• 4.2 Check Intent state - PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL PASS

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

• 12.1 Add back s5 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Topology view is correct and consistent across all ONOS nodes - FAIL PASS
• 8.4 Checking ONOS nodes - 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

• 4.1 Ping across added host intents - FAIL PASS
• 4.2 Check Intent state - PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL PASS

Case 13: Test Cleanup - PASS

...