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.
...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCnetCfg_onos-2.2_20-builds_graph.jpg", alt="FUNCnetCfg", style="width:525px;height:350px;border:0"> |
commit a30877e1eb778f32d5f5201ab5c255bc9d97c195 94a5d1778f2a92c59f3259292e5cce5da01a4d87 (HEAD -] onos-2.2, origin/onos-2.2)
Author: Andrea Campanella pier [andrea@opennetworkingpier@opennetworking.org]
AuthorDate: Thu Nov 28 14:31:02 Tue Dec 10 18:09:00 2019 +0100
Commit: Andrea Campanella pier [andrea@opennetworkingpier@opennetworking.org]
CommitDate: Fri Nov 29 Jan 17 13:0648:15 2019 55 2020 +0000
Avoid propagating a null chassisID
--
(cherry picked from commit f468858e9104e49e83c6294fdc4d17ce9456d7fd)0100
Fix VERIFY timeout
Case 1: Pull onos branch and build onos on Teststation. - 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 Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Creating ONOS package - PASS
- 2.5 Installing Atomix - PASS
- 2.6 Installing ONOS package - PASS
- 2.7 Set up ONOS secure SSH - PASS
- 2.8 Checking ONOS service - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - 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 - PASS
- 21.1 Check net config - PASS
- 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
...
- 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 - PASS
- 23.1 Check net config - PASS
- 23.2 ONOS should only show devices S1 and S2 - PASS
- 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