...
Note: Network Slicing use case involves deploying lots of components. Depends Depending on the system you are using, the no. number of pods you have started to start might exceed the max-pod allowance of the system, which will cause a lots of pods to be 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.
...
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.
The scripts regarding dedicated to the network slicing locates are located in folder test/pythonsdk/src/orantests/network_slicing.
...
The command will trigger the main script test_network_slicing.py, which further in turn 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 located in the folder network_slicing/preparation.
...
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.
...