UPDATE IN PROGRESS
This page describes how to run various NONRTRIC functions in Docker.
...
Details of the architecture can be found from Release IJ page.
Table of Contents | ||
---|---|---|
|
...
In general, there is no need to build the images manually unless there are code changes made by the user, so release images should be used. Instruction on how to build all components, see. Release I J - Build.
The run commands throughout this page uses the release images and tags. Replace the release images/tags in the container run commands in the instructions if manually-built snapshot images are desired.
...
J Release - Images & Tags
...
|
Wait 1 minute to allow the container to start and to read the configuration. Then run the command below another terminal. The output should match the configuration in the file - all three rics (ric1, ric2 and ric3) should be included in the output. Note that each ric has the state "UNAVAILABLE" until the simulators are started.
Note: If the policy management service is started with config for the SDNC A1 Controller (the second config option), do the steps described in section Run the SDNC A1 Controller Docker Container below before proceeding.
NOTE: Use below Endpoint to use a1policymanagement V2
|
...
|
...
This step is only applicable if the configuration for the Policy Management Service include the SDNC A1 Controller (second config option), see Run the A1 Policy Management Service Docker NOTE: Use below Endpoint to use a1policymanagement V3
|
Expected output (not that all simulators - ric1,ric2 and ric3 will indicate "state":"UNAVAILABLE" until the simulators has been started in Run A1 Simulator Docker Containers):
|
Run the SDNC A1 Controller Docker Container (ONAP SDNC)
Anchor | ||||
---|---|---|---|---|
|
This step is only applicable if the configuration for the Policy Management Service include the SDNC A1 Controller (second config option), see Run the A1 Policy Management Service Docker Container.
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-compose.yaml
Code Block | ||
---|---|---|
| ||
version: '3' networks: default: external: true name: nonrtric-docker-net services: db: image: nexus3.o-ran-sc.org:10001/mariadb:10.5 container_name: sdncdb networks: - default ports: - "3306" environment: - MYSQL_ROOT_PASSWORD=itsASecret - MYSQL_ROOT_HOST=% - MYSQL_USER=sdnctl - MYSQL_PASSWORD=gamma - MYSQL_DATABASE=sdnctl logging: driver: "json-file" options: max-size: "30m" max-file: "5" a1controller: image: nexus3.onap.org:10001/onap/sdnc-image:2.56.41 depends_on : - db container_name: a1controller networks: - default entrypoint: ["/opt/onap/sdnc/bin/startODL.sh"] ports: - 8282:8181 - 8443:8443 links: - db:dbhost - db:sdnctldb01 - db:sdnctldb02 environment: - MYSQL_ROOT_PASSWORD=itsASecret - MYSQL_USER=sdnctl - MYSQL_PASSWORD=gamma - MYSQL_DATABASE=sdnctl - SDNC_CONFIG_DIR=/opt/onap/sdnc/data/properties - SDNC_BIN=/opt/onap/sdnc/bin - ODL_CERT_DIR=/tmp - ODL_ADMIN_USERNAME=admin - ODL_ADMIN_PASSWORD=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U - ODL_USER=admin - ODL_PASSWORD=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U - SDNC_DB_INIT=true - A1_TRUSTSTORE_PASSWORD=a1adapter - AAI_TRUSTSTORE_PASSWORD=changeit logging: driver: "json-file" options: max-size: "30m" max-file: "5" |
...
Start a simulator for each ric
defined in in the application_configuration.json
created above in section Run the A1 Policy Management Service Docker Container. Each simulator will use one of the currently available A1 interface versions. Each simulator uses different local ports.
ric1
|
...
|
ric2
|
ric2
ric3
|
ric3
...
docker run --rm --network=nonrtric-docker-net -p
8087:8085 -p 8187:8185 -e A1_VERSION=STD_2.0.0 -e ALLOW_HTTP=
true
--name=ric3 nexus3.o-ran-sc.org:10002
/o-ran-sc/a1-simulator
:2.5.0
...
|
Wait at least one minute to let the policy management service synchronise the ric
s. Then run the command below another terminal. The output should match the configuration in the file. Note that each ric
now has the state "AVAILABLE
".
NOTE: Use below Endpoint to use a1policymanagement V2
|
Expected output - all state should indicated AVAILABLE
:
|
NOTE: Use below Endpoint to use a1policymanagement V3
|
Expected output - all state should indicated AVAILABLE
:
|
...
List the synchronised types using a1policymanagement V2 endpoint:
|
...
|
List the synchronised types using a1policymanagement V3 endpoint:
|
Expected output:
|
Run the Information Coordinator Service Docker Container
Anchor | ||||
---|---|---|---|---|
|
...
|
Verify that the Information Coordinator Service is started and responding (response is an empty array).
...
|
Verify that the service is up and running
...
|
Setup jobs to produce data according to the types in application_configuration.json
...
Start the CAPIF Core (Release HJ) in a separate shell with the following command:
|
This is a basic start command without helm. See CAPIF (Release H) and the README file in the sme repository for more options.
...