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

HAswapNodes at 01 Jun 2016 04:45:07

commit fc4ef00d9dd109a422144e1f4dd29441c846790a (HEAD, origin/onos-1.6, onos-1.6)
Author: Thomas Vachuska [tom@onlab.us]
AuthorDate: Tue May 31 17:59:59 2016 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Jun 1 01:20:12 2016 +0000

Fixing javadocs.

Case 1: Setting up test environment - PASS

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 Checking ONOS nodes - PASS (tick)
  • 1.14 Activate apps defined in the params file - No Result (warning)
  • 1.15 Set ONOS configurations - PASS (tick)
  • 1.16 App Ids check - PASS (tick)

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 - PASS (tick)
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 28 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 - PASS (tick)
  • 3.2 Check app ids - PASS (tick)
  • 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 8: Compare ONOS Topology view to Mininet topology - 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 - 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)
  • No labels