Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/HASanity/166/

...

commit 7b438afd38ed9e22d04876679ba0e644c66607a5 a92936379381dc6a6f90652cd9638659f8c2cacf (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska Hari Krishna [tom@onlabhari@onlab.us]
AuthorDate: Tue Thu Jul 7 0916 16:5243:07 40 2015 -0700
Commit: Thomas Vachuska [tom@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Fri Jul 15 1917 03:0921:56 01 2015 -0700
Initial sketch of the virtual network constructs.+0000

wipe-out command changes to purge intents
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HASanity/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - PASS (tick)
  • 8.8 Device information is correct - PASS (tick)
  • 8.9 Links are correct - PASS (tick)
  • 8.10 Hosts are correct - PASS (tick)
  • 8.11 Checking ONOS nodes - PASS (tick)

Case 7: Running ONOS Constant State Tests -

...

PASS

  • 7.1 Check that each switch has a master - PASS (tick)
  • 7.2 Read device roles from ONOS - PASS (tick)
  • 7.3 Check for consistency in roles from each controller - PASS (tick)
  • 7.4 Compare switch roles from before failure - PASS (tick)
  • 7.5 Get the intents and compare across all nodes - PASS (tick)
  • 7.6 Check for consistency in Intents from each controller - PASS (tick)
  • 7.7 Compare current intents with intents before the failure - PASS (tick)
  • 7.8 Get the OF Table entries and compare to before component failure - PASS (tick)
  • 7.9 Check the continuous pings to ensure that no packets were dropped during component failure - FAIL (error)
    • Loss of dataplane connectivity detected
  • PASS (tick)
  • 7.10 Leadership Election is still functional - PASS (tick)

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

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

...

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - PASS (tick)
  • 8.8 Device information is correct - PASS (tick)
  • 8.9 Links are correct - PASS (tick)
  • 8.10 Hosts are correct - PASS (tick)
  • 8.11 Checking ONOS nodes - PASS (tick)

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

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

...

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - PASS (tick)
  • 8.8 Device information is correct - PASS (tick)
  • 8.9 Links are correct - PASS (tick)
  • 8.10 Hosts are correct - PASS (tick)
  • 8.11 Checking ONOS nodes - PASS (tick)

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

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

...

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - PASS (tick)
  • 8.8 Device information is correct - PASS (tick)
  • 8.9 Links are correct - PASS (tick)
  • 8.10 Hosts are correct - PASS (tick)
  • 8.11 Checking ONOS nodes - PASS (tick)

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

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

...

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - PASS (tick)
  • 8.8 Device information is correct - PASS (tick)
  • 8.9 Links are correct - PASS (tick)
  • 8.10 Hosts are correct - PASS (tick)
  • 8.11 Checking ONOS nodes - PASS (tick)

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

Case 13: Test Cleanup - PASS

...