...
step 1: Deploy ONAP components using SMO starting script
Start the platform for the use case, we could use the SMO starting scripts. If you don't have an idea about what SMO starting scripts are, please have a read of the SMO package introduction and watch the attached videos first.
...
Note: Network Slicing use case involves deploying lots of components. Depends on the system you are using, the no. of pods you have started might exceed the max-pod allowance of the system, which will cause lots of pods in status Pending. If using "kubectl describe" to show the details of the pod, you will see error message of "too many pods". Increasing the max-pod number to 200 will solve the issue. Different system set max pod in different ways. With microk8s you can open file /var/snap/microk8s/current/args/kubelet, add the line "--max-pods=200" at the end of the file, restart the service with command service snap.microk8s.daemon-kubelite restart and verify whether the date has been updated with command kubectl describe node <node_value> | grep -i capacity -A 13.
step 2: Run use case preparation scripts to configure all the components
The preparation scripts are python scripts, based on the ONAP pythonsdk framework. The detailed introduction of the framework can be found in the SMO package introduction.
...
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.
step 3: Starting needed simulators
Network Slicing Option2 use case involves 3 simulators: external core NSSMF simulator, ACTN simulator and external RAN NSSMF simulator. SMO packages prepares the lab using helm charts, but unfortunately there are no helm chart available yet for those 3 simulators, so they should be started manually at this moment.
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.
step 4 : Run test script and verify the result
When typing the tox command, it first runs the preparation scripts and then triggers the real testing script.
...