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/439/

...

commit 858ad8ca146710ca3d99641bf9ac27309b127aea 68aaad547eabececaa582da23216a41131d8b57a (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.necCharles Chan [rascov@gmail.com]
AuthorDate: Thu Fri Dec 8 109 12:5954:33 49 2016 -0800
Commit: Yuta HIGUCHI [y-higuchi@ak.jp.nec.comCharles Chan [charles@onlab.us]
CommitDate: Fri Mon Dec 9 1912 23:3824:14 48 2016 -0800
Add netcfg event to event history+0000

Determines route IP by checking the interface config directly
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 21.1 Assign mastership of switches to specific controllers - PASS (tick)
  • 21.2 Check mastership was correctly assigned - PASS (tick)

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 (tick)
  • 3.2 Check app ids - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - PASS (tick)
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - FAIL (error)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 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - FAIL (error)
  • Intents have not been installed correctly, pings failed.
  • 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 5: Setting up and gathering data for current state -

...

PASS

  • 5.1 Check that each switch has a master - FAIL (error)
    • Some devices don't have a master assigned
  • PASS (tick)
  • 5.2 Get the Mastership of each switch from each controller - FAIL (error)
    • Error in reading roles from ONOS
  • PASS (tick)
  • 5.3 Check for consistency in roles from each controller - PASS (tick)
  • 5.4 Get the intents from each controller - PASS (tick)
  • 5.5 5.3 Check for consistency in roles Intents from each controller - FAIL (error)
  • ONOS nodes have different views of switch roles
  • PASS (tick)
  • 5.4 6 Get the intents flows from each controller - FAIL (error)
  • Error in reading intents from ONOS
  • PASS (tick)
  • 5.7 Check for consistency in Flows from each controller - PASS (tick)
  • 5.8 Get the OF Table entries - No Result (warning)
  • 5.9 Start continuous pings - No Result (warning)
  • 5.10 Collecting topology information from ONOS - No Result (warning)
  • 5.11 Host view is consistent across ONOS nodes - PASS (tick)
  • 5.12 Each host has an IP address - PASS (tick)
  • 5.13 Cluster view is consistent across ONOS nodes - PASS (tick)
  • 5.14 Cluster view correct across ONOS nodes - PASS (tick)
  • 5.15 Comparing ONOS topology to MN - PASS (tick)
  • 5.16 Device information is correct - PASS (tick)
  • 5.17 Links are correct - PASS (tick)
  • 5.18 Hosts are correct - PASS (tick)

Case 14: Start Leadership Election app - FAIL

  • 14.1 Install leadership election app - PASS (tick)
  • 14.2 Run for election on each node - FAIL (error)
    • Inconsistent leaderboards

Case 16: Install Primitives app - PASS

  • 16.1 Install Primitives app - PASS (tick)