...
Java 11 (make sure that JAVA_HOME environment variable points to correct Java version)
Maven 3.6 (make sure you have configured maven to use the ONAP maven repositories)
Docker and docker-compose (latest)
Create Configuration for A1 Policy Management Service
Configure the A1 Policy Management Service
To support local test with two separate near-RT-RIC simulator instances:
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 "Build 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.
- It is optional to access the near-RT-RIC through a controller. The "controller" property is optional in the "ric" objects. If no controller is used, the whole "controller" object can be omitted.
There is no functional gain in accessing the near-RT-RIC through a controller.
Sample application configuration
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
{ "description": "Application configuration", "config": { "controller": [ { "name": "controller1", "baseUrl": "http://sdnc_controller:8181", "userName": "admin", "password": "Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" } ], "ric": [ { "name": "ric1", "baseUrl": "http://ric1:8085/", "managedElementIds": [ ] }, { "name": "ric2", "baseUrl": "http://ric2:8085/", "managedElementIds": [ "kista_3", "kista_4" ] }, { "name": "ric3", "baseUrl": "http://ric3:8085/", "controller": "controller1", "managedElementIds": [ "kista_5", "kista_6" ] }, { "name": "ric4", "baseUrl": "http://ric4:8085/", "controller": "controller1", "managedElementIds": [ "kista_7", "kista_8", "kista_9", "kista_10", "kista_11" ] } ] } } |
JSON Schema for the application configuration
The configuration must comply to the following JSON schema. There are several tools on internet where it is possible to validate JSON against a schema.
...