...
Code Block | ||||
---|---|---|---|---|
| ||||
$ docker images o-ran-sc/nonrtric-r-app-catalogue 1.0.1.0-SNAPSHOT o-ran-sc/nonrtric-enrichment-coordinator-service 1.0.1.0-SNAPSHOT o-ran-sc/nonrtric-policy-agent 2.21.01-SNAPSHOT |
Build near-rt-ric-simulator container
...
Code Block | ||
---|---|---|
| ||
cd a1-interface/near-rt-ric-simulator docker build -t near-rt-ric-simulator:latest . |
You can check that the image is in docker using:
Code Block | ||||
---|---|---|---|---|
| ||||
$ docker images
o-ran-sc/nonrtric-r-app-catalogue 1.0.1-SNAPSHOT
o-ran-sc/nonrtric-enrichment-coordinator-service 1.0.1-SNAPSHOT
o-ran-sc/nonrtric-policy-agent 2.1.1-SNAPSHOT
near-rt-ric-simulator latest |
Build NONRTRIC / A1 Policy control panel container
...
- Run docker container using this command once A1 Controller and simulators have been fully started:
docker run -p 8081:8081 -p 8433:8433 --network=nonrtric-docker-net --name=policy-agent-container o-ran-sc/nonrtric-policy-agent:2.21.01-SNAPSHOT
- Once policy-agent is up and running, it establishes connections to all configured Near-RT RICs
- If policy-agent-container is configured to log at DEBUG level, the following logs should appear to log to show that connection to the configured RICs has been established successfully via A1 Controller.
...
docker run -p 8083:8083 -p 8434:8434 --network=nonrtric-docker-net --name=enrichment-service-container o-ran-sc/nonrtric-enrichment-coordinator-service:1.0.1.0-SNAPSHOT
- Change directory:
cd nonrtric/docker-compose/data/testdata/ECS
- Put an example Enrichment information Producer by running these curl commands:
...
curl -X PUT -v "http://localhost:8083/A1-EI/v1/eijobs/job1" -H "accept: application/json" \
-H "Content-Type: application/json" --data-binary @EiProducer@EiJob.json
Run Non-RT RIC Control Panel Docker Container
...