Introduction

This wiki is meant to detail the steps to automate the Network Slicing use case testing using the O-RAN-SC SMO package.

...

https://github.com/sebdet/oran-deployment

step 1: Deploy ONAP components using SMO starting script

Start the platform for the use case, we could use the SMO starting scripts.

...

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.

...

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.

...

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.

...

If you want to continue the Network Slicing Option2 use case test, please run it manually.

Currently known issues

Currently the SMO package is based on the ONAP oom Jakarta release. There's already some known issues regarding the Network Slicing related code.

...

Restart the so-bpmn-infra pod with command "kubectl delete pod <onap-so-bpmn-infra-pod-name> -n onap"

Demos: