...
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.
Code Block | ||
---|---|---|
| ||
docker run --rm \ -v <absolute-path-to- |
...
file>/application_configuration.json:/opt/app/policy-agent/data/application_configuration.json \ -p 8081:8081 \ -p 8433:8433 \ --network=nonrtric-docker-net \ --name=policy-agent-container \ nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-a1policymanagementservice:2. |
...
9. |
...
0 |
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.
...
|
ric2
|
ric3
|
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
".
...
|
Verify that the Information Coordinator Service is started and responding (response is an empty array).
...