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_unexpected ONOS branchonos-2.2_20-builds_graph.jpg", alt="FUNCnetCfg", style="width:525px;height:350px;border:0"> |
commit 5fbf6bfe080b602de7263f1549090eef490c09ce d95d3524caff5449aded4ff9397c3ed717fc91e6 (HEAD, review/andrea_campanella/24493origin/onos-2.2, onos-2.2)
Author: Andrea Campanella Jian Li [andrea@opennetworkingpyguni@gmail.orgcom]
AuthorDate: Fri Mar 26 10:34Thu Aug 12 18:03:30 2021 +01000900
Commit: Andrea Campanella Jian Li [andrea@opennetworkingpyguni@gmail.orgcom]
CommitDate: Fri Mar 26 21:03:51 2021 +0100
[VOL-3922] Invalidating the pipeliner cache if the driver for a device changesThu Aug 12 18:58:19 2021 +0900
Add default route option to kubevirt network
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 5 node(s) ONOS cluster -
...
Set up ONOS with 5 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
...