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

HATestSanity at 27 May 2015 20:58:33

commit cd40e5b8e6e3295641de59c0579f5805192586e2 (HEAD, origin/master, origin/HEAD, master)
Author: Madan Jampani [madan@onlab.us]
AuthorDate: Wed May 27 17:19:48 2015 -0700
Commit: Madan Jampani [madan@onlab.us]
CommitDate: Wed May 27 18:44:56 2015 -0700

Refresh candidate board from source on each election round + Disbale east-west synchronization of candidate board

Case 1: Setting up test environment - PASS

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

  • 1.1 Applying cell variable to environment - No Result (warning)
  • 1.2 Starting Mininet - PASS (tick)
  • 1.3 Git checkout and pull master - PASS (tick)
  • 1.4 Using mvn clean install - PASS (tick)
  • 1.5 Creating ONOS package - PASS (tick)
  • 1.6 Installing ONOS package - PASS (tick)
  • 1.7 Checking if ONOS is up yet - PASS (tick)
  • 1.8 App Ids check - PASS (tick)

Case 2: Assigning Controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device. Then manually assign mastership to specific ONOS nodes using 'device-role'

  • 2.1 Assign switches to controllers - PASS (tick)
  • 2.2 Assign mastership of switches to specific controllers - PASS (tick)
  • 2.3 Check mastership was correctly assigned - PASS (tick)

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

Compare topology objects between Mininet and ONOS

  • 8.1 Create TestONTopology object - PASS (tick)
  • 8.2 Comparing ONOS topology to MN - No Result (warning)
  • 8.3 Topology view is correct and consistent across all ONOS nodes - PASS (tick)
  • 8.4 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 - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - FAIL (error)
  • 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)
  • No labels