There are four versions of implementations for the "Hello World" O-RU O-DU Fronthaul Fronthaul Recovery usecase. This page describes how to run them.
| Table of Contents |
|---|
Standalone script version
The standalone script version of the usecase is implemented in python. With this version Helm charts are provided to run the usecase.
Prerequisits
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):
...
This 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.
Assumption:
It is assumed that the DMaaP Message Router is already running as a docker container with the hostname "onap-dmaap" and connected to the docker network named "nonrtric-docker-net". It is also assumed that a topic named "unauthenticated.SEC_FAULT_OUTPUT" has already been created in the Message Router.
Start the ONAP Policy framework
The ONAP Policy framework can be run in a stand-alone mode using the docker-compose in OSC nonrtric repo:
...
| Code Block | ||
|---|---|---|
| ||
docker-compose up -d |
Run SDNR-simulator
The apex policy will make a REST call to the SDNR-simulator for sending the configuration messages. The code for SDNR simulator is available in the nonrtric repo. Run the following commands to build the docker image for SDNR-simulator:
...
| Code Block | ||
|---|---|---|
| ||
docker run --rm --name sdnr-sim --network nonrtric-docker-net -e MR-HOST="http://onap-dmaap" -e MR-PORT="3904" sdnr-simulator:1.0.0 |
Create/Deploy apex policy for O-RU & O-DU use case
All the ingredients of apex policy designed for O-RU & O-DU use case are available here:
...
| Code Block | ||
|---|---|---|
| ||
docker logs policy-apex-pdp |
Workflow for updating the policy config
In case some changes need to be made in the policy config (located in /config directory), a new ToscaPolicy.json file (located in /deployment directory) has to be generated for deploying the apex policy. The new file can be created by using the apexCLIToscaEditor.sh script in the policy-apex-pdp docker container via the following steps:
...
- After running the above command, the ToscaPolicy.json file is automatically updated in the /deployment directory of nonrtric in the host where docker is running.
Information Coordinator Job consumer version in Go
This version of the usecase is implemented as an Information Coordinator Service (ICS) job consumer, and is implemented in Go. It provides three simulators, shown in the picture below.
...
To start the simulators and the consumer, pull the nonrtric repo, https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric and follow the instructions in the dmaap-mediator-producer/README.md file.
Information Coordinator Job consumer version in Java
This version of the usecase is implemented as an Information Coordinator Service (ICS) job consumer, and is implemented in Java. To run the usecase, start the simulators according to the instructions for the Go version and then start the consumer by following the instructions in the dmaap-adaptor-java/README.md file.