...
In general, you can run the scripts under layer-0 to install the needed software on your lab. Then trigger script under layer-1 to build all the needed helm chart.
At last, go to folder layer-2 and run the following command to deploy the components needed for networt-slicing option2 use case.
...
The command above will take configuration parameters from onap-override.yaml under folder helm-override/network-slicing. If you want different configurations, please update them in the onap-override.yaml file.
The deployment will take about 1 hour to be fully started and stabilized, since it involves lots of components. Before going to the next step, please make sure all the components are running OK.
...
The scripts regarding the network slicing locates in folder test/pythonsdk/src/orantests/network_slicing.
Before running the script, please open settings.py under folder test/pythonsdk/src/orantests/configuration. Make sure the URL settings for all the components are the good values. To make it work, you can either update the settings.py using the correct IP/hostname or update /etc/hosts of the lab adding the IP/hostname mappings.
If the settings are good, go to folder test/pythonsdk/src/orantests/network-slicing and run the following command to trigger the preparation script:
...
The command will trigger the main script test_network_slicing.py, which further triggers the preparation script of each component. The whole preparation process will configure the components and also verifies a bit whether the configuration was done successfully at the end of each step. The whole process may take about 1 hour to complete. You can monitor the progress using the log file pythonsdk.debug.log at folder network_slicing/preparation.
If everything goes fine, you will see similar logs as shown below in the end.
If things goes wrong, please read the logs to identify which part has go wrong and try to fix that step manually. Then you can update the test_network_slicing.py, disable steps that are already complete, and replay the tox command to complete the rest of the configuration.
...
Please note, when checking test_network_slicing.py in details, you will find some of the preparation steps might require extra input parameters, such as cst_id, cst_invariant_id and sp_id. These values could be found in both logs and SDC UI.
In case it failed in the middle of the SDC template creation, please update the sdc_template_suffix variable inside the test_network_slicing.py and then rerun the script with tox command. Since SDC doesn't support creating template with the same name, neither deleting of any templates, you have to add a suffix to the original name to create template with a new name.
Starting needed simulators
...
It is in our plan to create helm chart for those 3 simulators and put them under tests_oom folder, so that they could be deployed easily using SMO starting script in the future.
Run test script and verify the result
...
At this moment, the method is still empty. We are still progressing in the testing script. If you want to continue the Network Slicing Option2 use case test, please run it manually.
Currently known issues
...
Add the line “uwsgi_read_timeout 300;” under the Server section
Restart oof-has-api pod with command "kubectl delete pod <onap-oof-has-api-pod-name> -n onap"
...
name: onap-oof-config
subPath: interfaces.py
- key: interfaces.py
path: interfaces.py
2) SO timeout issue
The details of the issue is described in JIRA ticket SO-3968. There fixing is still in progress.
...
Find out the oof timeout settings under override.yaml file and updated the value to PT15m
Restart the so-bpmn-infra pod with command "kubectl delete pod <onap-so-bpmn-infra-pod-name> -n onap"