...
To execute the Policy Management Service you will need an “application_configuration.json” file to configure the service.
This configuration file is then mounted into the correct place in the docker container using the -v parameter above (-v "application_configuration.json:/opt/app/policy-agent/application_configuration.json")
- For more information on configuration options see page: Release B - Build/Run
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"config": {
"//description": "Application configuration",
"controller": [
{
"name": "a1-controller",
"baseUrl": "http://a1-controller:8181",
"userName": "admin",
"password": "Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U"
}
],
"ric": [
{
"name": "ric1",
"baseUrl": "http://a1-sim-OSC:8085/",
"controller": "a1-controller",
"managedElementIds": [
"kista_1",
"kista_2"
]
},
{
"name":"ric2",
"baseUrl":"http://a1-sim-STD:8085/",
"controller": "a1-controller",
"managedElementIds":[
"kista_3",
"kista_4"
]
}
]
}
} |
...
(This assumes that the near-RT-RIC "ric1" uses a version of the A1 protocol that supports Policy Types (e.g. OSC-A1-v2.1.0), and the near-RT-RIC supports Policy Type "1", and the data passed for the Policy object complies with the schema for that Policy Type.)
...
(This assumes that the near-RT-RIC "ric2" uses a version of the A1 protocol that does not support Policy Types (e.g. A1-AP-v1.1) but the data passed for the Policy object can be interpreted by the near-RT-RIC)
...