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

HAsingleInstanceRestart at 26 Jul 2017 14:04:08

commit cfef6f9963093b87c7f8b16a10392be63f409d91 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Tue Jul 25 16:58:42 2017 -0700
Commit: Simon Hunt [simon@onlab.us]
CommitDate: Tue Jul 25 16:58:53 2017 -0700

ONOS-6833: UiPreferencesService: augment to include getPreferences(username, prefsKey)

Case 1: Starting up 1 node(s) ONOS cluster - PASS

Set up ONOS with 1 node(s) ONOS cluster

  • 1.1 Constructing test variables - PASS (tick)
  • 1.2 Apply cell to environment - PASS (tick)
  • 1.3 Uninstalling ONOS package - PASS (tick)
  • 1.4 Create cell file - No Result (warning)
  • 1.5 Applying cell variable to environment - No Result (warning)
  • 1.6 Starting Mininet - PASS (tick)
  • 1.7 Create cell file - No Result (warning)
  • 1.8 Applying cell variable to environment - No Result (warning)
  • 1.9 Creating ONOS package - PASS (tick)
  • 1.10 Installing ONOS package - PASS (tick)
  • 1.11 Set up ONOS secure SSH - PASS (tick)
  • 1.12 Starting ONOS service - PASS (tick)
  • 1.13 Starting ONOS CLI sessions - PASS (tick)
  • 1.14 Checking ONOS nodes - PASS (tick)
  • 1.15 Activate apps defined in the params file - No Result (warning)
  • 1.16 Set ONOS configurations - PASS (tick)
  • 1.17 Check app ids - 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 - PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - PASS (tick)
  • 8.2 Checking ONOS nodes - PASS (tick)

Case 3: Adding host Intents - PASS

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 ) - PASS (tick)
  • 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 - PASS (tick)

Case 4: Verify connectivity by sending traffic across Intents - PASS

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 - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

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 - PASS (tick)
  • 5.3 Check for consistency in roles from each controller - PASS (tick)
  • No labels