Page History

...

commit eaa97825d3b54f0680cc29c9a732b25f8a2955f5 26333deb459163a667427806d4ac4315ce4277fb (HEAD, origin/onos-1.6, onos-1.6)
Author: Simon Hunt [simon@onlab.usPrince Pereira [prpereir@partner.ciena.com]
AuthorDate: Wed Aug 24 1117 16:4125:02 13 2016 -0700+0530
Commit: Simon Hunt [simon@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Fri Aug 24 1626 18:4035:02 2016 -0700
Cleaned up urlBase() readability.
--
(cherry picked from commit fa875bb)
31 2016 +0000

Fix for ONOS-4834. Created rest api for removing the flows using appid, device id and flowid.

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

...

• 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 - PASS
• 20.2 Add Net Cfg for switch3 - PASS
• 20.3 Check net config - PASS 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

...

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

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

...

FAIL

• 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 - PASS FAIL
• Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
• 27.5 ONOS should only show devices S1, S2, S4, S5 and S6 - PASS
• 27.6 Modify json object so S6 is disallowed - PASS

...

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

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

...

FAIL

• 21.1 Check net config - PASS FAIL
• 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
• 21.3 Check device annotations - PASS

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
• 22.2 Add Net Cfg for switch4 - PASS
• 22.3 Check net config - PASS FAIL
• 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 - PASS FAIL
• Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
• 23.2 ONOS should only show devices S1 and S2 - PASS
• 23.3 Check device annotations - PASS

Case 24: Testing removal of configurations -

...

FAIL

• 24.1 Remove 'allowed' configuration from all devices - PASS
• 24.2 Check net config - PASS FAIL
• Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
• 24.3 Delete basic config for s1 and s2 - PASS
• 24.4 Check net config - PASS FAIL
• Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
• 24.5 Delete the net config for S3 - PASS
• 24.6 Check net config - PASS FAIL
• Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
• 24.7 Delete the net config for all devices - PASS
• 24.8 Check net config - PASS FAIL
• Net Cfg is different on some nodes. Some nodes failed to GET netCfg.
• 24.9 Assert the net config for devices is empty - PASS