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

FUNCnetCfg at 06 Jun 2016 20:58:00

commit 403b577ccdc00c0a11859c8f41d266a6d769a801 (HEAD, origin/onos-1.6, onos-1.6)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Mon Jun 6 16:51:11 2016 -0700
Commit: Simon Hunt [simon@onlab.us]
CommitDate: Mon Jun 6 16:51:11 2016 -0700

ONOS-4359: continued work on theming UI

Case 1: Constructing test variables and building ONOS package - PASS

This test case is mainly for loading from params file, and pull and build the latest ONOS package

  • 1.1 Constructing test variables - PASS (tick)

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

Set up ONOS with 7 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Creating ONOS package - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Installing ONOS package - PASS (tick)
  • 2.5 Starting ONOS service - PASS (tick)

Case 20: Add Network configurations to the cluster - FAIL

Add Network Configurations for devices not discovered yet. One device is allowed, the other disallowed.

  • 20.1 Add Net Cfg for switch1 - PASS (tick)
  • 20.2 Add Net Cfg for switch3 - PASS (tick)
  • 20.3 Check net config - FAIL (error)
    • Net Cfg is different on some nodes.

Case 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly

  • 11.1 Starting Mininet topology with OF 1.3 switches - PASS (tick)

Case 21: Check Devices After they initially connect to ONOS - FAIL

  • 21.1 Check net config - FAIL (error)
    • Net Cfg is different on some nodes.
  • 21.2 ONOS should only show devices S1, S2, and S4 - PASS (tick)
  • 21.3 Check device annotations - PASS (tick)

Case 22: Add Network configurations for connected devices to the cluster - FAIL

Add Network Configurations for discovered devices. One device is allowed, the other disallowed.

  • 22.1 Add Net Cfg for switch2 - PASS (tick)
  • 22.2 Add Net Cfg for switch4 - PASS (tick)
  • 22.3 Check net config - FAIL (error)
    • Net Cfg is different on some nodes.

Case 23: Check Devices after all configurations are set - FAIL

  • 23.1 Check net config - FAIL (error)
    • Net Cfg is different on some nodes.
  • 23.2 ONOS should only show devices S1 and S2 - FAIL (error)
    • ONOS devices doesn't match the list of allowed devices.
    • Expected devices: ['of:0000000000000001', 'of:0000000000000002']
    • Actual devices: ['of:0000000000000001', 'of:0000000000000002', 'of:0000000000000004']
  • 23.3 Check device annotations - FAIL (error)
    • Incorrect annotations for configured devices.

Case 24: Testing removal of configurations - FAIL

  • 24.1 Remove 'allowed' configuration from all devices - PASS (tick)
  • 24.2 Check net config - FAIL (error)
    • Net Cfg is different on some nodes.
  • 24.3 Delete basic config for s1 and s2 - PASS (tick)
  • 24.4 Check net config - FAIL (error)
    • Net Cfg is different on some nodes.
  • 24.5 Delete the net config for S3 - PASS (tick)
  • 24.6 Check net config - FAIL (error)
    • Net Cfg is different on some nodes.
  • 24.7 Delete the net config for all devices - PASS (tick)
  • 24.8 Check net config - FAIL (error)
    • Net Cfg is different on some nodes.
  • 24.9 Assert the net config for devices is empty - PASS (tick)
  • No labels