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 436 Next »

HAsanity at 19 Apr 2016 23:37:16

commit d77c8810f4fe67711d7bdb171173a1c5e8d4246a (HEAD, origin/master, origin/HEAD, master)
Author: Ray Milkey [ray@onlab.us]
AuthorDate: Tue Apr 19 13:06:00 2016 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Apr 20 00:35:08 2016 +0000

Buck build bugfixes

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 - No Result (warning)
  • 1.3 Starting Mininet - PASS (tick)
  • 1.4 Git checkout and pull master - No Result (warning)
  • 1.5 Using mvn clean install - PASS (tick)
  • 1.6 Creating ONOS package - PASS (tick)
  • 1.7 Installing ONOS package - PASS (tick)
  • 1.8 Checking if ONOS is up yet - PASS (tick)
  • 1.9 Checking ONOS nodes - FAIL (error)
    • Nodes check NOT successful
  • 1.10 Activate apps defined in the params file - No Result (warning)
  • 1.11 Set ONOS configurations - PASS (tick)
  • 1.12 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 - FAIL (error)
    • ONOS nodes have different views of hosts
  • 8.3 Hosts information is correct - FAIL (error)
    • Host information is incorrect
  • 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 2 SCCs
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - FAIL (error)
    • Hosts are incorrect
  • 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 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 - FAIL (error)
    • ONOS nodes have different views of hosts
  • 8.3 Hosts information is correct - FAIL (error)
    • Host information is incorrect
  • 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 11 SCCs
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - FAIL (error)
    • Hosts are incorrect
  • 8.10 Checking ONOS nodes - FAIL (error)
    • Nodes check NOT successful

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 - FAIL (error)
    • Error looking up host ids
  • 3.7 Intent Anti-Entropy dispersion - FAIL (error)

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 - FAIL (error)
    • Intents are not all in INSTALLED state
  • 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 - FAIL (error)
    • Some devices don't have a master assigned
  • 5.2 Get the Mastership of each switch from each controller - FAIL (error)
    • Error in reading roles from ONOS
  • 5.3 Check for consistency in roles from each controller - FAIL (error)
    • ONOS nodes have different views of switch roles
  • 5.4 Get the intents from each controller - FAIL (error)
    • Error in reading intents from ONOS
  • 5.5 Check for consistency in Intents from each controller - FAIL (error)
    • ONOS nodes have different views of intents
  • 5.6 Get the flows from each controller - FAIL (error)
    • Error in reading flows from ONOS
  • No labels