...
For more details about running the OSC A1 Simulator see the related OSC NONRTRIC Wiki page (Release IJ) and OSC A1 Simulator Documentation (I Release)
...
Run A1 Policy Management Service docker container using the command below, after the A1-Controller and simulators have been fully started.
It may be useful to set the logging level toTRACE
level, where you can verify the A1-Controller, A1-Simualtors and A1 Policy Management Service is fully up and running.
The configuration file (application_configuration.json described above) must be mounted as avolume
into the container, so absolute path and name of the file must be substituted in the following command:Code Block language bash title Docker: Run the A1 Policy Management Service docker run -p 8081:8081 --network=nonrtric-docker-net --name=a1policymanagmentservice --volume **<Absolute path to application_configuration.json created above>**:/opt/app/policy-agent/data/application_configuration.json nexus3.onap.org:10002/onap/ccsdk-oran-a1policymanagementservice:1.67.10
Note: Version numbers used in this page may not be the most recent ... you should verify the latest version numbers for released pre-built components in the docker image repository (https://nexus3.onap.org)
Code Block language bash title Optional: Enable TRACE level logging in A1 Policy Management Service collapse true curl -X POST http://localhost:8081/actuator/loggers/org.onap.ccsdk.oran.a1policymanagementservice -H "Content-Type:application/json" -d {\"configuredLevel\":\"trace\"}
Once the Policy Management Service is up and running, it establishes connections to all configured near-RT-RICs (
ric1
,ric2
,ric3
,ric4
) via the A1 Controller.If the
a1policymanagmentservice
container is configured to log atTRACE
level, the following logs entries should appear indicating that connection to the configured RICs has been established successfully via A1 Controller.
...
For more examples of using the NONRTRIC Control panel see Montreal New Delhi - Testing end-to-end callcall to A1 Interface