...
Copy the file oran/a1-policy-management/config/application_configuration.json to the current directory and update it with the configuration below.
(Note the configuration below is just a sample, and should be updated to match particular deployments. The deployment below assumes 4 near-RT-RICs exist - addressable at the urls given.)The controller hostname and port values come from and must match those defined in in the sdnc/oam repo oam/installation/src/main/yaml/docker-compose.yml (see the step "Run A1 Controller" further below). The port for http is 8181.
(Note the configuration below is just a sample, and should be updated to match particular deployments. The deployment below assumes an A1 Controller function (SDNC) exists - addressable at the url given, using the authentication credentials given.)Any defined ric host names (in the name and baseUrl for each ric) must match the given docker container names in near-RT-RIC simulator startup - port is always the simulator's internal port 8085 for http or 8185 for https.
- The A1 Policy Management service can entirely by-pass the A1-Controller if required - it is optional to access the near-RT-RIC through an A1-Controller.
In the configuration the "controller" property is optional in the "ric" objects, and the "controller" object at the top can be omitted if no controller is used.
If all configured rics bypass the A1-Controller there is no need to start an A1-Controller. There is no functional gain in accessing the near-RT-RIC through an A1 controller.
...