...

Firstly, the common steps for creating control loops for both apex policy and script versions of the usecase are described. This is followed by the steps that are unique for setting up and testing each version individually. 

Create topic in

...

DmaaP MR

The following need to be installed to run the script according to these instructions:

• Docker
• Kubernetes
• Helm 3

Run

To run the script for the O-RU & O-DU Fronthaul Recovery use case with necessary simulators, download the repo (defaults to master branch): 

     git clone "https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric"

     git checkout dawn --track origin/e-release

Go to the folder:

  cd nonrtric/test/usecases/oruclosedlooprecovery/scriptversion/helm

Run the following command:

   ./start.sh

In order to create the fault notification topic in DMaaP Message Router, the first step is to find out its NodePort and NodeIP. The NodeIP is the IP address of any k8s node in the cluster where ONAP has been installed, and it can be found using the command "kubectl get nodes -o wide". The NodePort can be found using the command "kubectl -n onap get svc | grep message-router-external". Next, the topic defined for this usecase can be created using:

curl -k -X POST -H "Content-Type: application/json" -d "{"topicName": "unauthenticated.SEC_FAULT_OUTPUT"}" https://<NodeIP>:<NodePort-message-router>/events/unauthenticated.SEC_FAULT_OUTPUT

Run Policy GUI

The easiest way to create the control loops is via Policy GUI component of the clamp. The below steps describe how to start this GUI.

NOTE: At the time of writing this page (15 Dec 2021), there is a bug in the helm chart of policy/clamp in 'istanbul' branch of OOM. The bug should be fixed by the policy/clamp team. Until then, the following steps should be done to fix this problem. Run the command:

kubectl -n onap edit cm def-policy-clamp-be-configmap

(whereas "def" refers to the name of deployment and should be replaced with the name used when installing ONAP. The same should be done for all instructions given below that use "def" as deployment name)

and change http to https in clamp.config.controlloop.runtime.url under application.properties. Then, run this command:

kubectl rollout restart deployment def-policy-clamp-be

Next step is to find out the NodePort of policy-guy. This can be done by using the command "kubectl -n onap get svc | grep policy-gui".

Then, open a web browser and navigate to the url:

https://<NodeIP>:<NodePort-policy-gui>/clamp/

Use below credentials for the GUI:

username: demo@people.osaaf.org.                 password: demo123456!

Image Added

Start-up screen of the Policy GUI

Commission/Instantiate control loop via GUI

This sub-section shows how to commission and instantiate the control loops via policy-gui. The individual tosca templates for each of the apex policy and script versions are provided below in the relevant sub-sections. The screenshots shown in this sub-section are general steps that are applicable for both versionsThis will build the script and the simulators and then start them all.

Apex Policy version

This version is run in the stand-alone ONAP policy framework and uses an apex policy.

...