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/HAfullNetPartition/117/

...

commit 375f4be24a2b1bf84114d254a6e03965d9a604b6 ed804d51445888ea3b7fce38b80c24496b670471 (HEAD, origin/master, origin/HEAD, master)
Author: Charles Chan Simon Hunt [rascov@gmailsimon@onlab.comus]
AuthorDate: Tue Wed Mar 29 1530 09:5351:59 40 2016 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Wed Mar 29 2330 22:2422:57 21 2016 +0000
Add .buckd and buck-out into .gitignore
Initial cut for UI topo model implementation.
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=1&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 6 4 SCCs
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Checking ONOS nodes - PASS (tick)

...

  • 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 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - FAIL (error)
    • ONOS nodes have different views of intents
  • 7.6 Compare current intents with intents before the failure - FAIL (error)
    • The Intents changed during failure
  • PASS (tick)
  • 7.7 Get the OF Table entries and compare to before component failure - FAIL (error)
    • Changes were found in the flow tables
  • PASS (tick)
  • 7.8 Leadership Election is still functional - PASS (tick)

Case 4: Verify connectivity by sending 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 - FAIL (error)
  • Intents are not all in INSTALLED 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 - FAIL

...

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 3 SCCs
  • PASS (tick)
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • PASS (tick)
  • 8. 8.9 Checking ONOS nodes - PASS (tick)

...

  • 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 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - FAIL (error)
    • ONOS nodes have different views of intents
  • 7.6 Compare current intents with intents before the failure - FAIL (error)
    • The Intents changed during failure
  • 7.7 Get the OF Table entries and compare to before component failure - FAIL (error)
    • Changes were found in the flow tables
  • 7.8 Leadership Election is still functional - PASS (tick)

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 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - FAIL (error)
  • Intents are not all in INSTALLED 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 - FAIL

...

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 3 SCCs
  • PASS (tick)
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - FAIL (error)
  • Links are incorrect
  • PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

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 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - FAIL (error)
    • Intents are not all in INSTALLED 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.

...

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 3 SCCs
  • PASS (tick)
  • 8. 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - FAIL (error)
  • Links are incorrect
  • PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sending 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 - FAIL (error)
    • Intents are not all in INSTALLED 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 switch to ensure it is discovered correctly - PASS

...

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
  • ONOS shows 3 SCCs
  • PASS (tick)
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - FAIL (error)
  • Links are incorrect
  • PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sending 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 - FAIL (error)
  • Intents are not all in INSTALLED 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 topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
  • ONOS shows 3 SCCs
  • PASS (tick)
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sending 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 - FAIL (error)
  • Intents are not all in INSTALLED 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

...