Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/FUNC-pipeline-master/1353/

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCnetCfg_master_20-builds_graph.jpg", alt="FUNCnetCfg", style="width:525px;height:350px;border:0">

commit 411bf2e9bb7e259e601c47eebcbe67e748677c06 1e39bd2f4444f6662898a936fa1944d5aa35718e (HEAD -] master, origin/master, origin/HEAD)
Author: Jian Li Thomas Vachuska [pyguni@gmailtom@opennetworking.comorg]
AuthorDate: Thu Nov 29 00:08:54 2018 +0900Fri Dec 14 14:47:53 2018 -0800
Commit: Jian Li Thomas Vachuska [pyguni@gmailtom@opennetworking.comorg]
CommitDate: Fri Dec 14 14 02:4247:25 53 2018 +0000
Refactor: resolve code smells of openstacknetworking impl pkgs #3-0800

Allowing cell-stc to inherit stcOpenJDK env. variable.

Case 1: Pull onos branch and build onos on Teststation. - PASS

...

  • 25.1 Moving network-cfg.json to $ONOS_ROOT/tools/package/config/ - PASS (tick)

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

...

Set up ONOS with 3 node(s) ONOS cluster

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Creating ONOS package - PASS (tick)
  • 2.5 Installing Atomix - PASS (tick)
  • 2.6 Installing ONOS package - PASS (tick)
  • 2.7 Set up ONOS secure SSH - PASS (tick)
  • 2.8 Checking ONOS service - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)

Case 20: Add Network configurations to the cluster - PASS

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

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 27: Posting network configurations to the top level web resource - PASS

  • 27.1 Get json object from Net Cfg - No Result (warning)
  • 27.2 Posting json object to Net Cfg - No Result (warning)
  • 27.3 Compare device with ONOS - No Result (warning)
  • 27.4 Check net config - PASS (tick)
  • 27.5 ONOS should only show devices S1, S2, S4, S5 and S6 - PASS (tick)
  • 27.6 Modify json object so S6 is disallowed - 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, and S5 - 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 - PASS

  • 21.1 Check net config - PASS (tick)
  • 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 - PASS

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

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

  • 23.1 Check net config - PASS (tick)
  • 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 - PASS

...

FAIL