Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

HAswapNodes at 23 Jun 2016 23:46:46

commit e56d38d2d11a6e0cb040aef9ee8fb1bbbca3d0cf (HEAD, tag: 1.6.0-rc5)
Author: Brian O'Connor [bocon@onlab.us]
AuthorDate: Thu Jun 23 19:06:19 2016 -0700
Commit: Brian O'Connor [bocon@onlab.us]
CommitDate: Thu Jun 23 19:06:50 2016 -0700

Tagging 1.6.0-rc5

Case 1: Setting up test environment - FAIL

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

  • 1.1 Create cell file - No Result (warning)
  • 1.2 Applying cell variable to environment - PASS (tick)
  • 1.3 Verify connectivity to cell - PASS (tick)
  • 1.4 Setup server for cluster metadata file - PASS (tick)
  • 1.5 Generate initial metadata file - PASS (tick)
  • 1.6 Starting Mininet - PASS (tick)
  • 1.7 Git checkout and pull master - No Result (warning)
  • 1.8 Using mvn clean install - PASS (tick)
  • 1.9 Copying backup config files - PASS (tick)
  • 1.10 Creating ONOS package - PASS (tick)
  • 1.11 Installing ONOS package - PASS (tick)
  • 1.12 Checking if ONOS is up yet - PASS (tick)
  • 1.13 Starting ONOS CLI sessions - FAIL (error)
    • ONOS cli startup failed
  • 1.14 Checking ONOS nodes - PASS (tick)
  • 1.15 Activate apps defined in the params file - No Result (warning)
  • 1.16 Set ONOS configurations - FAIL (error)
    • Failed to set config
  • 1.17 App Ids check - FAIL (error)
    • Something is wrong with app Ids

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

  • 2.1 Assign switches to controllers - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 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 27 SCCs
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - FAIL (error)
    • Nodes check NOT successful

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

  • 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 - 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 - FAIL (error)
    • Install fwd failed
  • 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 - FAIL (error)
    • Uninstall fwd failed
  • 3.5 Check app ids - FAIL (error)
    • Something is wrong with app Ids
  • 3.6 Add host intents via cli - FAIL (error)
    • Error looking up host ids
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 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 22 SCCs
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 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 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 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.

Case 5: Setting up and gathering data for current state - No Result

  • 5.1 Check that each switch has a master - PASS (tick)
  • 5.2 Get the Mastership of each switch from each controller - 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 Check for consistency in Intents from each controller - PASS (tick)
  • 5.6 Get the flows from each controller - 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 - FAIL (error)
    • ONOS nodes have different views of hosts
  • 5.12 Each host has an IP address - PASS (tick)
  • No labels