FUNCnetCfg at 27 Feb 2018 22:11:02

<img src="https://onos-jenkins.onlab.us/job/Pipeline_postjob_VM/lastSuccessfulBuild/artifact/FUNCnetCfg_unexpected ONOS branch_20-builds_graph.jpg", alt="FUNCnetCfg", style="width:525px;height:350px;border:0">
commit 611f466a833c3622ade16aceec509bde3490a87d (HEAD, origin/master, origin/HEAD)
Author: Thomas Vachuska [tom@opennetworking.org]
AuthorDate: Tue Feb 27 11:30:09 2018 -0800
Commit: Thomas Vachuska [tom@opennetworking.org]
CommitDate: Wed Feb 28 01:01:14 2018 +0000

Fixing issue in component config subsystem where the locally registered
--
(cherry picked from commit a3b55a90bb6b09d80ae486bf8a53ae028db2aafa)

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

For loading from params file, and pull and build the latest ONOS package

Case 25: Preparing network-cfg.json to load configurations - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

Case 20: Add Network configurations to the cluster - PASS

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

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

Case 27: Posting network configurations to the top level web resource - PASS

Case 26: Check to see if the pre-startup configurations were set, then remove their allowed status - PASS

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

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.

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

Case 24: Testing removal of configurations - PASS