Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
FUNCnetCfg at 13 Oct 2017 20:28:35
commit 09220c20d74cc008c4d8319a1ed4a6be2518f63c (HEAD, origin/master, origin/HEAD, master)
Author: Pier Luigi [pierventre@hotmail.com]
AuthorDate: Thu Sep 14 22:00:30 2017 +0200
Commit: Andrea Campanella [andrea@opennetworking.org]
CommitDate: Fri Oct 13 18:41:09 2017 +0000
[ONOS-7003] Policer implementation
Case 1: Pull onos branch and build onos on Teststation. - PASS
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 Uninstalling ONOS package - PASS
- 2.3 Creating ONOS package - PASS
- 2.4 Installing ONOS package - PASS
- 2.5 Set up ONOS secure SSH - PASS
- 2.6 Checking ONOS service - PASS
- 2.7 Starting ONOS CLI sessions - PASS
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
- 20.2 Add Net Cfg for switch3 - PASS
- 20.3 Check net config - PASS
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 - PASS
- 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
- 27.5 ONOS should only show devices S1, S2, S4, S5 and S6 - PASS
- 27.6 Modify json object so S6 is disallowed - PASS
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
- 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
- 21.2 ONOS should only show devices S1, S2, and S4 - FAIL
- ONOS devices doesn't match the list of allowed devices
- 21.3 Check device annotations - 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.
- 22.1 Add Net Cfg for switch2 - PASS
- 22.2 Add Net Cfg for switch4 - PASS
- 22.3 Check net config - PASS
Case 23: Check Devices after all configurations are set - FAIL
- 23.1 Check net config - PASS
- 23.2 ONOS should only show devices S1 and S2 - FAIL
- ONOS devices doesn't match the list of allowed devices.
- Expected devices: ['of:0000000000000001', 'of:0000000000000002']
- Actual devices: ['of:0000000000000001', 'of:0000000000000002', 'of:0000000000000005']
- 23.3 Check device annotations - PASS
Case 24: Testing removal of configurations - PASS
- 24.1 Remove 'allowed' configuration from all devices - PASS
- 24.2 Check net config - PASS
- 24.3 Delete basic config for s1 and s2 - PASS
- 24.4 Check net config - PASS
- 24.5 Delete the net config for S3 - PASS
- 24.6 Check net config - PASS
- 24.7 Delete the net config for all devices - PASS
- 24.8 Check net config - PASS
- 24.9 Assert the net config for devices is empty - PASS