This page describes how to run current implementation for the O-DU Slice Assurance usecase.
Standalone script version
The standalone script version of the usecase is implemented in Golang.
It provides a simulator that stub both Dmaap MR and SDNR (orange boxes in the picture below), so both processes can share its data.
Prerequisites
The following need to be installed to run the script according to these instructions:
- Go must be installed, see https://go.dev/doc/install.
- Pull the nonrtric repo, https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric.
Run
Run Dmaap MR / SDNR stub
This stub has been coded on Go, similar to the simulator used in O-RU O-DU Closed loop recovery use case previously described. However, this stub simulates both Dmaap VES messages and also SDNC. By default, the stub listens to port 3905, can be changed with the flag "--sdnr-port".
To run the stub, follow the steps below:
- Goto "test/usecases/odusliceassurance/goversion/stub" in the repo.
- Build the stub, "go build".
- Start the stub, "./stub"
cd nonrtric/test/usecases/odusliceassurance/goversion/stub go build ./stub [--sdnr-port <portNo>] [--dmaap-port <portNo>] Example: └─ $ ▶ ./sdnr --sdnr-port 3906 Starting DmaapMR stub on port: 3905 Starting SDNR stub on port: 3606
Run O-DU Slice Assurance Rapp
The application takes a number of environment variables for configuration, but only MR_HOST and MR_PORT are required, others are optional. More information can be found in README.md file
cd nonrtric/test/usecases/odusliceassurance/goversion/ go build ./oduclosedloop
Environment variables can be defined as part of the command line as follow:
Example: └─ $ ▶ MR_HOST=http://localhost MR_PORT=3905 ./oduclosedloop