Master-FUNCnetCfg

commit a402038459b95d0864cc389b6454102b45ea7170 (HEAD -] master, origin/master, origin/HEAD)
Author: Saurav Das [sauravdas@alumni.stanford.edu]
AuthorDate: Wed Feb 14 14:14:54 2018 -0800
Commit: Saurav Das [sauravdas@alumni.stanford.edu]
CommitDate: Fri Mar 2 16:20:53 2018 -0800

Handling multiple layers of spines.
--
Also in this commit:
- Triggering swap group creation and accounting for it in DestinationSet
- Fixes in ofdpa2 and ofdpa3 pipeline to allow SR Continue operation
- Renaming mplsSet in DestinationSet to notBos
- Removing unused RandomDestinationSet
- Bug fix in ofdpa driver for swap group chain creation
- Bug fix in ofdpa driver for verify group operation

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 $ONOS_ROOT/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 - 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 - FAIL
• Check Net Cfg failed. Check above messages.

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 - 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 - FAIL
• Check Net Cfg failed. Check above messages.
• 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 - FAIL
• Check Net Cfg failed. Check above messages.
• 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 - FAIL
• Check Net Cfg failed. Check above messages.

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

• 23.1 Check net config - FAIL
• Check Net Cfg failed. Check above messages.
• 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 - FAIL
• Check Net Cfg failed. Check above messages.
• 24.3 Delete basic config for s1 and s2 - PASS
• 24.4 Check net config - FAIL
• Check Net Cfg failed. Check above messages.
• 24.5 Delete the net config for S3 - PASS
• 24.6 Check net config - FAIL
• Check Net Cfg failed. Check above messages.
• 24.7 Delete the net config for all devices - PASS
• 24.8 Check net config - FAIL
• Check Net Cfg failed. Check above messages.
• 24.9 Assert the net config for devices is empty - PASS