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

FUNCnetCfg at 05 Jul 2016 02:05:04

commit 614cf2978b81a0510fed2ade371cc96d66ad5763 (HEAD, origin/onos-1.6, onos-1.6)
Author: Carmelo Cascone [carmelo@onlab.us]
AuthorDate: Wed Jun 29 16:15:04 2016 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Jul 1 16:38:51 2016 +0000

BMv2 device friendly name set during device discovery

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 25: Preparing network-cfg.json to load configurations - PASS

  • 25.1 Moving network-cfg.json to /home/sdn/onos/tools/package/config/ - 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. Some nodes failed to GET netCfg.

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 26: Check to see if the pre-startup configurations were set, then remove their allowed status - PASS

  • 26.1 Checking configurations for Switches 5 and 6 - No Result (warning)
  • 26.2 ONOS should only show devices S1, S2, S4, S5, and S6 - PASS (tick)
  • 26.3 Removing allowed status from Switches 5 and 6 - No Result (warning)

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. Some nodes failed to GET netCfg.
  • 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. Some nodes failed to GET netCfg.

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

  • 23.1 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • 23.2 ONOS should only show devices S1 and S2 - PASS (tick)
  • 23.3 Check device annotations - PASS (tick)

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. Some nodes failed to GET netCfg.
  • 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. Some nodes failed to GET netCfg.
  • 24.5 Delete the net config for S3 - PASS (tick)
  • 24.6 Check net config - FAIL (error)
    • Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
  • 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. Some nodes failed to GET netCfg.
  • 24.9 Assert the net config for devices is empty - PASS (tick)
  • No labels