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/HAswapNodes/291/

...

commit 1dc6adf9a9d211fdc96785abf2acb0d62fa62b2c f9e9865b8327cace039f40591607ddb59738e450 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt Charles Chan [simon@onlabrascov@gmail.uscom]
AuthorDate: Fri Oct 14 14:47:45 Wed Sep 7 16:54:23 2016 -0700
Commit: Simon Hunt [simon@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Mon Oct 14 1417 20:4731:45 2016 -0700
Region Sample Topo - renamed stuff and updated lat/long11 2016 +0000

Initial commit of new Ofdpa3Pipeline

This submission also addresses the following issues
* CORD-84 Restore is_present bit to 1 in set_vlan_vid
* CORD-338 Remove default route workaround

MPLS Termination fix is coming in another patch.
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAswapNodes/plot/Plot-HA/getPlot?index=2&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 6.1 Checking ONOS Logs for errors - No Result (warning)
  • 6.2 Generate new metadata file - PASS (tick)
  • 6.3 Start new nodes - PASS (tick)
  • 6.4 Checking if ONOS is up yet - PASS (tick)
  • 6.5 Starting ONOS CLI sessions - PASS (tick)
  • 6.6 Checking ONOS nodes - FAIL (error)
    • Failed to rerun for election
  • 6.7 Reapplying cell variable to environment - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - PASS (tick)
  • 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 - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

Case 3: Adding host Intents - FAIL

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 - FAIL (error)
    • Something is wrong with app Ids
  • 3.3 Discovering Hosts( Via pingall for now ) - FAIL (error)
    • Reactive Pingall failed, one or more ping pairs failed
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - FAIL (error)
    • Something is wrong with app Ids
  • 3.6 Add host intents via cli - PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - FAIL (error)

Case 7: Running ONOS Constant State Tests - No Result

  • 7.1 Check that each switch has a master - FAIL (error)
    • Some devices don't have a master assigned
  • 7.2 Read device roles from ONOS - FAIL (error)
    • Error in reading roles from ONOS
  • 7.3 Check for consistency in roles from each controller - FAIL (error)
    • ONOS nodes have different views of switch roles
  • 7.4 Get the intents and compare across all nodes - FAIL (error)
    • Error in reading intents from ONOS