Page History

DRAFT - This page describes how to get the release E version of Non-RT RIC up and running locally with three separate Near-RT RIC A1 simulator docker containers providing STD_1.1.3, STD_2.0.0 and OSC_2.1.0 versions of the A1 interface.

All components of the Non-RT RIC run as docker containers and communicate via a private docker network with container ports, ports also available on localhost. Details of the architecture can be found from Release E page.

Project Requirements

• Docker and docker-compose (latest)

• kubectl with admin access to kubernetes (minikube, docker-desktop kubernetes etc)  -  this is only applicable when running the Helm Manager
• helm with access to kubernetes - this is only applicable when running the Helm Manager example operations

Images

The images used for running the Non-RT RIC can be selected from the table below depending on if the images are built manually (snapshot image) or if staging or release images shall be used.

...

Ports

The following ports will be allocated and exposed to localhost for each component. If other port(s) are desired, then the ports need to be replaced in the container run commands in the instructions further below.

...

Prerequisites

The containers need to be connected to docker network in order to communicate with each other.

...

docker network create nonrtric-docker-net

Run the Policy Management Service Docker Container

To support local test with three separate Near-RT RIC A1 simulator instances, each running a one of the three available A1 Policy interface versions:  

...

For troubleshooting/verification purposes you can view/access the full swagger API from url: http://localhost:8081/swagger-ui/index.html?configUrl=/v3/api-docs/swagger-config

Run the SDNC A1 Controller Docker Container (ONAP SDNC)

This step is only applicable if the configuration for the Policy Management Service include the SDNC A1 Controller (second config option), see Draft - Release E - Run.

Create the docker compose file - be sure to update image for the a1controller to the one listed for SDNC A1 Controller in the table on the top of this page.

...

docker exec a1controller sh -c "tail -f /opt/opendaylight/data/log/karaf.log"

Run the Near-RT RIC A1 Simulator Docker Containers

Start a simulator for each ric defined in in the application_configuration.json created in Draft - Release E - Run. Each simulator will use one of the currently available A1 interface versions.

...

{"policytype_ids":["","123","std_pt1"]}

Run the Information Service Docker Container

Run the following command to start the information coordinator service.

...

For troubleshooting/verification purposes you can view/access the full swagger API from url: http://localhost:8083/swagger-ui/index.html?configUrl=/v3/api-docs/swagger-config

Run the Non-RT RIC Gateway and Control Panel Docker Container

The Gateway exposes the interfaces of the Policy Management Service and the Inform Coordinator Service to a single port of the gateway. This single port is then used by the control panel to access both services.

...

The webbased UI can be accessed by pointing the web-browser to this URL: 

http://localhost:8080/

Run the App Catalogue Service Docker Container

Start the App Catalogue Service by the following command.

...

[ ]

Run the Helm Manager Docker Container

Note: Access to kubernetes is required as stated the requirements on the top of this page.

...

To run in the helm manager in kubernetes see this page:  Run Helm Manager in kubernetes

Run the Dmaap Adaptor Service Docker Container

The Dmaap Adaptor Service needs two configurations files, one for the application specific parameters and one for the types the application supports.

...

Data posted on the kafka topic unauthenticated.dmaapadp_kafka.text will be delivered to the path as specified in the job1.json.

Run the Dmaap Mediator Producer Docker Container

The Dmaap Mediator Producer needs one configuration file for the types the application supports.

...

Data posted on the message router topic unauthenticated.dmaapmed.json will be delivered to the path as specified in the jo2.json

Run usecases

Within NON-RT RIC a number of usecase implementations are provided. Follow the links below to see how to run them.

...