...
- The following step is required only if you want to run more than the default ric1 nearRT-RIC simulator instance
- replace the content of nonrtric/policy-agent/config/application_configuration.yaml json with the configuration below
- any defined ric names must match the given docker container names in nearRT-RIC simulator startup - port is always the simulator's internal 8085
...
- Start docker containers for each ric defined in nonrtric/policy-agent/config/application_configuration.yaml json in previous steps using following commands (in this example for ric1 and ric2):
docker run -p 8085:8085 --network=nonrtric-docker-net --name=ric1 o-ran-sc/near-rt-ric-simulator:1.0.1-SNAPSHOT
docker run -p 8086:8085 --network=nonrtric-docker-net --name=ric2 o-ran-sc/near-rt-ric-simulator:1.0.1-SNAPSHOT - Change directory to:
cd nonrtric/near-rt-ric-simulator/ric-plt/a1 - Put an example policy_type into all the started near-rt-ric-simulator instances by running these curl commands (in this example to ric1 exposed to port 8085 and ric2 exposed to port 8086):
curl -X PUT -v "http://localhost:8085/policytypes/STD_QoSNudging_0.2.0" -H "accept: application/json" \
-H "Content-Type: application/json" --data-binary @policy_type_STD_QoSNudging_0.2.0.json
curl -X PUT -v "http://localhost:8086/policytypes/STD_QoSNudging_0.2.0" -H "accept: application/json" \
-H "Content-Type: application/json" --data-binary @policy_type_STD_QoSNudging_0.2.0.json
...