DRAFT
This page describes how to get the release F G version of Non-RT RIC up and running locally with locally with three separate A1 simulator (previously called Near-RT RIC A1 Interface) 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 G page.
Table of Contents |
---|
Project Requirements
...
...
- Ports
- Prerequisites
- Run the A1 Policy Management Service Docker Container
- Run the SDNC A1 Controller Docker Container (ONAP SDNC)
- Run the A1 Simulator (previously called Near-RT RIC A1 Interface) Docker Containers
- Run the Information Coordinator Service Docker Container
- Run the Non-RT RIC Gateway and Control Panel Docker Container
- Run the App Catalogue Service Docker Container
- Run the Helm Manager Docker Container
- Run the Dmaap Adapter Service Docker Container
- Run the Dmaap Mediator Producer Docker Container
- Run usecases
Docker and docker-compose (latest)
- Additional optional requirements if using the "Helm Manager" function
- kubernetes v1.19+
- kubectl with admin access to kubernetes (minikube, docker-desktop kubernetes etc)
- helm with access to kubernetes - this is only applicable when running the Helm Manager example operations
Images
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 release images shall be used.
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 F G - 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.
...
G Maintenance Release images
Component | Image | Tag |
---|---|---|
A1 Policy Management Service | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-a1policymanagementservice | 2.5.0 |
Information Coordinator Service | nexus3 nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-informationcoordinatorservice | 1.4.0 |
NONRTRIC Control Panel | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-controlpanel | 2.4.0 |
Gateway | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-gateway | 1.0.0 |
A1-Simulator | nexus3.o-ran-sc.org:10002/o-ran-sc/a1-simulator | 2.4.0 |
R-APP Catalogue | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-rappcatalogue | 1.1.0 |
R-APP Catalogue Enhanced | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-rappcatalogue-enhanced | 1.0.1 |
DMaaP Adapter | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-dmaapadapter | 1.2.0 |
DMaaP Mediator | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-dmaapmediatorproducer | 1.1.0 |
Helm Manager | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-helmmanager | 1.2.0 |
Auth Token Fetcher | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-auth-token-fetch | 1.0.0 |
CAPIF Core | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-capifcore:1.0.0 | 1.0.0 |
O-DU Slice Assurance | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-rapp-ransliceassurance | 1.2.0 |
O-DU Slice Assurance | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-rapp-ransliceassurance-icsversion | 1.1.0 |
O-RU FH Recovery | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-rapp-orufhrecovery | 1.1.0 |
O-RU FH Recovery | nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-rapp-orufhrecovery-consumer | 1.1.0 |
Note: A version of this table appears Integration&Testing - F G Release Docker Image List - NONRTRIC (FG-Release). This is the authoritative version!
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.
...
Component | Port exposed to localhost (http/https) |
---|---|
A1 Policy Management Service | 8081/8443 |
A1 Simulator (previously called Near-RT RIC A1 Interface) | 8085/8185, 8086/8186, 8087/8187 |
Information Coordinator Service | 8083/8434 |
Non-RT RIC Control Panel | 8080/8880 |
SDNC A1-Controller | 8282/8443 |
Gateway | 9090 (only http) |
App Catalogue Service | 8680/8633 |
Helm Manager | 8112 (only http) |
Dmaap Mediator Producer | 9085/9185 |
Dmaap Adapter Service | 9087/9187 |
Capifcore | 8090 (only http) |
Prerequisites
The containers need to be connected to docker network in order to communicate with each other.
...
|
Run the A1 Policy Management Service Docker Container
To support local test with three separate A1 simulator (previously called Near-RT RIC A1 Interface) instances, each running a one of the three available A1 Policy interface versions:
- Create an application_configuration.json file with the configuration below. This will configure the policy management service to use the simulators for the A1 interface
- Note: Any defined ric names must match the given docker container names in near-RT RIC simulator startup, see Run A1 (previously called Near-RT RIC A1 Interface) Simulator Docker Containers
- The application supports both REST and DMAAP interface. REST is always enabled but to enable DMAAP (message exchange via message-router) additional config is needed. The examples below uses REST over http.
The policy management service can be configure with or without a A-Controller. Choose the appropriate configuration below.
...
The A1 Policy Mnagement Service can be configured to support A1 connection via an SDNC A1-Controller for some or all rics/simulators. It is optional to access the near-RT-RIC through an A1-Controller.
This is configured using the optional "controller" paramter for each ric entry. If all configured rics bypass the A1-Controller (do not have "controller" values) then the "controller" object at the top of the configuration can be omitted. If all configured rics bypass the A1-Controller there is no need to start an A1-Controller.
This sample configuration is for running without the SDNC A1-Controller
Code Block | ||
---|---|---|
| ||
{ |
...
"config": |
...
{ "ric": |
...
[ { "name": |
...
"ric1", |
...
"baseUrl": |
...
"http://ric1:8085/", |
...
"managedElementIds": |
...
[ "kista_1", |
...
"kista_2" |
...
] }, { "name": |
...
"ric2", |
...
"baseUrl": |
...
"http://ric2:8085/", |
...
"managedElementIds": |
...
[ "kista_3", |
...
"kista_4" |
...
] }, { "name": |
...
"ric3", |
...
"baseUrl": |
...
"http://ric3:8085/", |
...
"managedElementIds": |
...
[ "kista_5", |
...
"kista_6" |
...
]
}
]
}
} |
This sample configuration This file is for running with the SDNC A1-Controller.
Code Block | ||
---|---|---|
| ||
{ |
...
"config": |
...
{ "controller": |
...
[ { "name": |
...
"a1controller", |
...
"baseUrl": |
...
"https://a1controller:8443", |
...
"userName": |
...
"admin", |
...
"password": |
...
"Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" |
...
} ], "ric": |
...
[ { "name": |
...
"ric1", |
...
"baseUrl": |
...
"http://ric1:8085/", |
...
"controller": "a1controller", "managedElementIds": |
...
[ "kista_1", |
...
"kista_2" |
...
] }, { "name": |
...
"ric2", |
...
"baseUrl": |
...
"http://ric2:8085/", |
...
"controller": |
...
"a1controller", |
...
"managedElementIds": [ "kista_3", |
...
"kista_4" |
...
] }, { "name": "ric3", "baseUrl": "http://ric3:8085/", |
...
"controller": |
...
"a1controller", |
...
"managedElementIds": |
...
[ "kista_ |
...
To enable the also the optional DMaaP interface, add the following config (same level as the "ric" entry) to application_configuration.json.
Be sure to update http/host/port below to match the configuration of the used message router.
A1 Policy Management Service DMaaP interface is deprecated
Note: The DMaaP interface for the A1 Policy Management Service is now deprecated
...
5",
"kista_6"
]
}
]
}
} |
Note:The optional A1 Policy Management Service DMaaP interface is deprecated so this interface shall no longer be configured in the application_configuration.json.
Start the container with the following command. Replace "<absolute-path-to-file>" with the the path to the created configuration file in the command. The configuration file is mounted to the container. There will be WARN messages appearing in the log until the simulators are started.
|
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 A1 Controller Docker Container below before proceeding.
...
Expected output (not that all simulators - ric1,ric2 and ric3 will indicate "state":"UNAVAILABLE" until the simulators has been started in Run A1 (previously called Near-RT RIC A1 Interface) Simulator Docker Containers):
|
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 Run the 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.yamlStart the SNDC A1 controller with the following command, using the created
Code Block | ||
---|---|---|
|
...
|
|
Open this url in a web browser to verify that the SDNC A1 Controller is up and running. It may take a few minutes until the url is available.
http://localhost:8282/apidoc/explorer/index.html#/controller%20A1-ADAPTER-API
Username/password: admin/Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
The Karaf logs of A1 controller can be followed e.g. by using command
|
Run the A1 Simulator (previously called Near-RT RIC A1 Interface) Docker Containers
Start a simulator for each ric defined in in the application_configuration.json created in Run the Policy Management Service Docker Container. Each simulator will use one of the currently available A1 interface versions.
Ric1
|
Ric2
|
Ric3
|
Wait at least one minute to let the policy management service synchronise the rics. 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".
|
Expected output - all state should indicated AVAILABLE:
|
The simulators using version STD_2.0.0 and OSC_2.1.0 supports policy types. Run the commands below to add one policy types in ric1 and ric3.
Create the file with policy type for ric1
osc_pt1.json
Put the policy type to ric1 - should http response code 201
...
curl -X PUT -
v
"http://localhost:8085/a1-p/policytypes/123"
-H
"accept: application/json"
\
-H
"Content-Type: application/json"
--data-binary @osc_pt1.json
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:10002/onap/sdnc-image:2.4.2
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 the SNDC A1 controller with the following command, using the created docker-compose file.
|
Open this url in a web browser to verify that the SDNC A1 Controller is up and running. It may take a few minutes until the url is available.
http://localhost:8282/apidoc/explorer/index.html#/controller%20A1-ADAPTER-API
Username/password: admin/Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
The Karaf logs of A1 controller can be followed e.g. by using command
|
Run the A1 Simulator (previously called Near-RT RIC A1 Interface) Docker Containers
Start a simulator for each ric defined in in the application_configuration.json created in Run the Policy Management Service Docker Container. Each simulator will use one of the currently available A1 interface versions.
Ric1
|
Ric2
|
Create the file with policy type for ric3
std_pt1.json
Put the policy type to ric3 - should return http response code 201
|
Wait one minute to let the policy management service synchronise the types with the simulators.
List the synchronised types.
|
Expected output:
|
Run the Information Coordinator Service Docker Container
Run the following command to start the information coordinator service.
|
Verify that the Information Coordinator Service is started and responding (response is an empty array).
|
Expected output:
|
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.
Create the config file for the gateway.
application.yaml
Run the following command to start the gateway. Replace "<absolute-path-to-file>" with the the path to the created application.yaml.
...
docker run --
rm
-
v
<absolute-path-to-config-
file
>
/application
.yaml:
/opt/app/nonrtric-gateway/config/application
.yaml -p 9090:9090 --network=nonrtric-docker-net --name=nonrtric-gateway nexus3.o-ran-sc.org:10002
/o-ran-sc/nonrtric-gateway
:1.0.0
Run the following two commands to check that the services can be reached through the gateway
|
Expected output
|
Ric3
|
Wait at least one minute to let the policy management service synchronise the rics. 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".
|
Expected output - all state should indicated AVAILABLE:
|
Second command:
|
Expected output:
|
Create the config file for the control panel.
nginx.conf
Run the following command to start the control panel. Replace "<absolute-path-to-file>" with the the path to the created nginx.conf.
|
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.
|
Verify that the service is up and running
|
Expected output:
|
Run the Helm Manager Docker Container
Note: Access to kubernetes is required as stated the requirements on the top of this page.
Download the 'helm-manger' repo, Helm Manager.
|
Start the helm manger in a separate shell by the following command:
|
Make sure the app has started by listing the current charts - response should be empty json array.
|
To test the app further, start a helm chart repo and create a dummy helm chart
Start a chartmuseum chart repository in a separate shell
|
Add the chart repo to the helm manager by the following command:
|
Create a dummy helm chart for test and package the chart, and save this chart in chartmuserum:
|
The commands below show examples of operations towards the helm manager using the dummy chart.
As an alternative, run the script 'test.sh' to execute a full sequence of commands.
The simulators using version STD_2.0.0 and OSC_2.1.0 supports policy types. Run the commands below to add one policy types in ric1 and ric3.
Create the file with policy type for ric1
Code Block | ||||
---|---|---|---|---|
| ||||
{
"name": "pt1",
"description": "pt1 policy type",
"policy_type_id": 1,
"create_schema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "OSC_PT1_0.1.0",
"description": "QoS policy type",
"type": "object",
"properties": {
"scope": {
"type": "object",
"properties": {
"ueId": {
"type": "string"
},
"qosId": {
"type": "string"
}
},
"additionalProperties": false,
"required": [
"ueId",
"qosId"
]
},
"statement": {
"type": "object",
"properties": {
"priorityLevel": {
"type": "number"
}
},
"additionalProperties": false,
"required": [
"priorityLevel"
]
}
}
}
} |
Put the policy type to ric1 - should http response code 201
|
Create the file with policy type for ric3
Code Block | ||||
---|---|---|---|---|
| ||||
{
"policySchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "STD_QOS_0_2_0",
"description": "STD QOS policy type",
"type": "object",
"properties": {
"scope": {
"type": "object",
"properties": {
"ueId": {
"type": "string"
},
"qosId": {
"type": "string"
}
},
"additionalProperties": false,
"required": [
"ueId",
"qosId"
]
},
"qosObjectives": {
"type": "object",
"properties": {
"priorityLevel": {
"type": "number"
}
},
"additionalProperties": false,
"required": [
"priorityLevel"
]
}
}
},
"statusSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "STD_QOS_0.2.0",
"description": "STD QOS policy type status",
"type": "object",
"properties": {
"enforceStatus": {
"type": "string"
},
"enforceReason": {
"type": "string"
},
"additionalProperties": false,
"required": [
"enforceStatus"
]
}
}
} |
Put the policy type to ric3 - should return http response code 201
|
Wait one minute to let the policy management service synchronise the types with the simulators.
List the synchronised types.
|
Expected output:
|
Run the Information Coordinator Service Docker Container
Run the following command to start the information coordinator service.
|
Verify that the Information Coordinator Service is started and responding (response is an empty array).
|
Expected output:
|
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 Information Coordinator Service to a single port of the gateway. This single port is then used by the control panel to access both services.
Create the config file for the gateway.
Code Block | ||||
---|---|---|---|---|
| ||||
server:
port: 9090
spring:
cloud:
gateway:
httpclient:
ssl:
useInsecureTrustManager: true
wiretap: true
httpserver:
wiretap: true
routes:
- id: A1-Policy
uri: https://policy-agent-container:8433
predicates:
- Path=/a1-policy/**
- id: A1-EI-P
uri: https://information-service-container:8434
predicates:
- Path=/data-producer/**
- id: A1-EI-C
uri: https://information-service-container:8434
predicates:
- Path=/data-consumer/**
management:
endpoint:
gateway:
enabled: true
endpoints:
web:
exposure:
include: "gateway,loggers,logfile,health,info,metrics,threaddump,heapdump"
logging:
level:
ROOT: ERROR
org.springframework: ERROR
org.springframework.cloud.gateway: INFO
reactor.netty: INFO
file:
name: /var/log/nonrtric-gateway/application.log |
Run the following command to start the gateway. Replace "<absolute-path-to-file>" with the the path to the created application.yaml.
|
Run the following two commands to check that the services can be reached through the gateway
|
Expected output
|
Second command:
|
Expected output:
|
Create the config file for the control panel.
Code Block | ||||
---|---|---|---|---|
| ||||
events{}
http {
include /etc/nginx/mime.types;
resolver 127.0.0.11;
server {
listen 8080;
server_name localhost;
root /usr/share/nginx/html;
index index.html;
location /a1-policy/ {
set $upstream nonrtric-gateway;
proxy_pass http://$upstream:9090;
}
location /data-producer/ {
set $upstream nonrtric-gateway;
proxy_pass http://$upstream:9090;
}
location /data-consumer/ {
set $upstream nonrtric-gateway;
proxy_pass http://$upstream:9090;
}
location / {
try_files $uri $uri/ /index.html;
}
}
} |
Run the following command to start the control panel. Replace "<absolute-path-to-file>" with the the path to the created nginx.conf.
|
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.
|
Verify that the service is up and running
|
Expected output:
|
Run the App Catalogue Enhanced Service Docker Container
Start the App Catalogue Enhanced Service by the following command.
|
Verify that the service is up and running
|
Expected output:
|
Run the Helm Manager Docker Container
Note: Access to kubernetes is required as stated the requirements on the top of this page.
Download the 'helm-manger' repo, Helm Manager.
|
Start the helm manger in a separate shell by the following command:
|
Make sure the app has started by listing the current charts - response should be empty json array.
|
To test the app further, start a helm chart repo and create a dummy helm chart
Start a chartmuseum chart repository in a separate shell
|
Add the chart repo to the helm manager by the following command:
|
Create a dummy helm chart for test and package the chart, and save this chart in chartmuserum:
|
The commands below show examples of operations towards the helm manager using the dummy chart.
As an alternative, run the script 'test.sh' to execute a full sequence of commands.
|
To run in the helm manager in kubernetes see this page: Run Helm Manager in kubernetes
Run the Dmaap Adapter Service Docker Container
The Dmaap Adapter Service needs two configurations files, one for the application specific parameters and one for the types the application supports.
Note that a running Information Coordinator Service is needed for creating jobs and a running message router is needed for receiving data that the job can distribute to the consumer.
In addition, if the data is available on a kafka topic then an instance of a running kafka server is needed.
Create the file application.yaml with content below.
The following parameter need to be configured according to hosts and ports (these setting may need to adjusted to your environment)
- ics-base-url: https://information-service-container:8434
- dmaap-base-url: https://message-router:3905 (needed when data is received from the Dmaap message router)
- bootstrap-servers: message-router-kafka:9092 (needed when data is received on a kafka topic)
|
Run the DMaaP Adapter Service Docker Container
The DMaaP Adapter Service needs two configurations files, one for the application specific parameters and one for the types the application supports.
Note that a running Information Coordinator Service is needed for creating jobs and a running message router is needed for receiving data that the job can distribute to the consumer.
In addition, if the data is available on a kafka topic then an instance of a running kafka server is needed.
Create the file application.yaml with content below.
The following parameter need to be configured according to hosts and ports (these setting may need to adjusted to your environment)
- ics-base-url: https://information-service-container:8434/
- dmaap-base-url: https://message-router:3905/ (needed when data is received from the Dmaap message router)
- bootstrap-servers: message-router-kafka:9092 (needed when data is received on a kafka topic)
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
spring:
profiles:
active: prod
main:
allow-bean-definition-overriding: true
aop:
auto: false
management:
endpoints:
web:
exposure:
# Enabling of springboot actuator features. See springboot documentation.
include: "loggers,logfile,health,info,metrics,threaddump,heapdump"
springdoc:
show-actuator: true
logging:
# Configuration of logging
level:
ROOT: ERROR
org.springframework: ERROR
org.springframework.data: ERROR
org.springframework.web.reactive.function.client.ExchangeFunctions: ERROR
org.oran.dmaapadapter: INFO
file:
name: /var/log/dmaap-adapter-service/application.log
server:
# Configuration of the HTTP/REST server. The parameters are defined and handeled by the springboot framework.
# See springboot documentation.
port : 8435
http-port: 8084
ssl:
key-store-type: JKS
key-store-password: policy_agent
key-store: /opt/app/dmaap-adapter-service/etc/cert/keystore.jks
key-password: policy_agent
key-alias: policy_agent
app:
webclient:
# Configuration of the trust store used for the HTTP client (outgoing requests)
# The file location and the password for the truststore is only relevant if trust-store-used == true
# Note that the same keystore as for the server is used.
trust-store-used: false
trust-store-password: policy_agent
trust-store: /opt/app/dmaap-adapter-service/etc/cert/truststore.jks
# Configuration of usage of HTTP Proxy for the southbound accesses.
# The HTTP proxy (if configured) will only be used for accessing NearRT RIC:s
http.proxy-host:
http.proxy-port: 0
ics-base-url: https://information-service-container:8434
# Location of the component configuration file. The file will only be used if the Consul database is not used;
# configuration from the Consul will override the file.
configuration-filepath: /opt/app/dmaap-adapter-service/data/application_configuration.json
dmaap-base-url: https://message-router:3905
# The url used to address this component. This is used as a callback url sent to other components.
dmaap-adapter-base-url: https://dmaapadapterservice:8435
zip-output: false
# KAFKA boostrap server. This is only needed if there are Information Types that uses a kafkaInputTopic
kafka:
bootstrap-servers: message-router-kafka:9092 |
application.yaml Create the file application_configuration.json according to one of alternatives below.
application_configuration.json without kafka type
application
Code Block | ||
---|---|---|
| ||
{ |
...
"types": |
...
[ { "id": |
...
"ExampleInformationType", |
...
"dmaapTopicUrl": |
...
"/events/unauthenticated.dmaapadp.json/dmaapadapterproducer/msgs?timeout=15000&limit=100", |
...
"useHttpProxy": |
...
false
}
]
} |
Code Block | ||
---|---|---|
|
...
| |
{ |
...
"types": |
...
[ { "id": |
...
"ExampleInformationType", |
...
"dmaapTopicUrl": |
...
"/events/unauthenticated.dmaapadp.json/dmaapadapterproducer/msgs?timeout=15000&limit=100", |
...
"useHttpProxy": |
...
false }, { "id": |
...
"ExampleInformationTypeKafka", |
...
"kafkaInputTopic": |
...
"unauthenticated.dmaapadp_kafka.text", |
...
"useHttpProxy": |
...
false } ] } |
Start the Dmaap Adapter Service in a separate shell with the following command:
|
Setup jobs to produce data according to the types in application_configuration.json
Create a file job1.json with the job definition (replace paths <url-for-jod-data-delivery> and <url-for-jod-status-delivery> to fit your environment:
Code Block | ||
---|---|---|
| ||
{ |
...
"info_type_id": |
...
"ExampleInformationType", |
...
"job_result_uri": |
...
"<url-for-jod-data-delivery>", |
...
"job_owner": |
...
"job1owner", |
...
"status_notification_uri": |
...
"<url-for-jod-status-delivery>", |
...
"job_definition": {} |
...
} |
Create job1 for type 'ExampleInformationType'
|
Check that the job has been enabled - job accepted by the Dmaap Adapter Service
...
Create a file job2.json with the job definition (replace paths <url-for-jod-data-delivery> and <url-for-jod-status-delivery> to fit your enviroment:
Code Block | ||
---|---|---|
| ||
{ |
...
"info_type_id": |
...
"ExampleInformationTypeKafka", |
...
"job_result_uri": |
...
"<url-for-jod-data-delivery>", |
...
"job_owner": |
...
"job1owner", |
...
"status_notification_uri": |
...
"<url-for-jod-status-delivery>", |
...
"job_definition": {} |
...
} |
Create job2 for type 'ExampleInformationType'
|
Check that the job has been enabled - job accepted by the Dmaap Adapter Service
|
Check that the job has been enabled - job accepted by the Dmaap Adapter Service
|
Data posted on the kafka topic unauthenticated.dmaapadp_kafka.text will be delivered to the path as specified in the job2.json.
Run the Dmaap Mediator Producer Docker Container
The Dmaap Mediator Producer needs one configuration file for the types the application supports.
Note that a running Information Coordinator Service is needed for creating jobs and a running message router is needed for receiving data that the job can distribute to the consumer.
Create the file type_config.json with the content below:
type_config.json
|
There are a number of environment variables that need to be set when starting the application. See these example settings:
|
Data posted on the kafka topic unauthenticated.dmaapadp_kafka.text will be delivered to the path as specified in the job2.json.
Run the Dmaap Mediator Producer Docker Container
The Dmaap Mediator Producer needs one configuration file for the types the application supports.
Note that a running Information Coordinator Service is needed for creating jobs and a running message router is needed for receiving data that the job can distribute to the consumer.
Create the file type_config.json with the content below
Code Block | ||
---|---|---|
| ||
{
"types": [
{
"id": "STD_Fault_Messages",
"dmaapTopicUrl": "/events/unauthenticated.dmaapmed.json/dmaapmediatorproducer/STD_Fault_Messages?timeout=15000&limit=100"
}
]
} |
There are a number of environment variables that need to be set when starting the application. See these example settings:
INFO_COORD_ADDR=https://informationservice:8434
DMAAP_MR_ADDR=https://message-router:390
LOG_LEVEL=Debug
INFO_PRODUCER_HOST=https://dmaapmediatorservice
INFO_PRODUCER_PORT=8185
Start the Dmaap Mediator Producer in a separate shell with the following command:
|
...
|
...
|
...
Start the Dmaap Mediator Producer in a separate shell with the following command:
...
docker run --
rm
-
v
\
<absolute-path-to-config-
file
>
/type_config
.json:
/configs/type_config
.json \
-p 8885:8085 -p 8985:8185 --network=nonrtric-docker-net --name=dmaapmediatorservice \
-e
"INFO_COORD_ADDR=https://information-service-container:8434"
\
-e
"DMAAP_MR_ADDR=https://message-router:3905"
\
-e
"LOG_LEVEL=Debug"
\
-e
"INFO_PRODUCER_HOST=https://dmaapmediatorservice"
\
-e
"INFO_PRODUCER_PORT=8185"
\
nexus3.o-ran-sc.org:10002
/o-ran-sc/nonrtric-plt-dmaapmediatorproducer
:1.
1.0
|
Setup jobs to produce data according to the types in type_config.json
Create a file job3.json with the job definition (replace paths <url-for-jod-data-delivery> and <url-for-jod-status-delivery> to fit your environment:
Code Block | ||
---|---|---|
| ||
{
"info_type_id": "STD_Fault_Messages",
"job_result_uri": "<url-for-job-data-delivery>",
"job_owner": "job3owner",
"status_notification_uri": "<url-for-job-status-delivery>",
"job_definition": {}
} |
Create job3 for type 'ExampleInformationType'
|
Check that the job has been enabled - job accepted by the Dmaap Adapter Service
|
Data posted on the message router topic unauthenticated.dmaapmed.json will be delivered to the path as specified in the job3.json.
Run SME CAPIF Core
Start the CAPIF Core in a separate shell with the following command:
|
This is a basic start command without helm. See repo README for more options.
Check that the component has started.
|
Setup jobs to produce data according to the types in type_config.json
Create a file job3.json with the job definition (replace paths <url-for-jod-data-delivery> and <url-for-jod-status-delivery> to fit your environment:
job3.json
|
Create job3 for type 'ExampleInformationType'
|
Check that the job has been enabled - job accepted by the Dmaap Adapter Service
|
Data posted on the message router topic unauthenticated.dmaapmed.json will be delivered to the path as specified in the job3.json
Run usecases
Within NON-RT RIC a number of usecase implementations are provided. Follow the links below to see how to run them.
...
Run use cases
Within NON-RT RIC a number of use case implementations are provided. Follow the links below to see how to run them.
...