commit 4b4d2d9344e4989ebfbd5e259c5d8faebdcfb525 (HEAD, origin/master, origin/HEAD, master)
Author: Simon Hunt [simon@onlab.us]
AuthorDate: Mon May 1 18:54:01 2017 -0700
Commit: Simon Hunt [simon@onlab.us]
CommitDate: Mon May 1 18:54:15 2017 -0700

Web UI framework README's - added skeletons for remaining Util services.

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

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

• 25.1 Moving network-cfg.json to /home/sdn/onos/tools/package/config/ - PASS

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

Set up ONOS with 3 node(s) ONOS cluster

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

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 - FAIL
• Net Cfg for device s1 not correctly set
• 20.2 Add Net Cfg for switch3 - FAIL
• Net Cfg for device s3 not correctly set
• 20.3 Check net config - FAIL
• 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

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

• 27.1 Get json object from Net Cfg - No Result
• 27.2 Posting json object to Net Cfg - No Result
• 27.3 Compare device with ONOS - No Result
• 27.4 Check net config - FAIL
• Net Cfg is different on some nodes. Some nodes failed to GET netCfg.