This page describes how to get the Istanbul release version of A1-Policy functions up and running.
...
To support local test with four separate near-RT-RIC simulator instances:
Copy the file default configuration file oran/a1-policy-management/config/application_configuration.json to (Istanbul) to the current directory and update it , then replace/amend the configuration with the sample demo 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, port, username 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 password values to access the A1 controller must match the values configured for the SDNC-A1-Controller. (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.
...
| Component | Release image and version tag | Staging images and version tag | Manual snapshot (only available if manually built) and version tag |
|---|---|---|---|
| A1 Policy Management Service | nexus3.onap.org:10002/onap/ccsdk-oran-a1policymanagementservice:1.2.1 | nexus3.onap.org:10004/onap/ccsdk-oran-a1policymanagementservice:1.2.1-STAGING-latest | onap/ccsdk-oran-a1policymanagementservice:1.2.2-SNAPSHOT |
| SDNC image | nexus3.onap.org:10002/onap/sdnc-image:2.2.0 | nexus3.onap.org:10004/onap/sdnc-image:2.2.0-STAGING-latest | onap/sdnc-image:2.2.1-SNAPSHOT |
...
For troubleshooting/verification purposes you can view/access the A1 Policy Management Service (policy-agent) swagger API from url: http://localhost:8081/swagger-ui.html (Note: the hostname may be different depending on your environment)
Run OSC Non-RT RIC Control Panel Docker Container
...
http://localhost:8080/ (Note: the hostname may be different depending on your environment)
The A1 policy Policy type pre-configured in the simulator should be visible (read-only) in the Control Panel display. Instances of the policy type can now be created, updated and deleted.
(Note: A1 policy types can only be created or deleted directly in the near-RT-RIC (or simulators), which will then be synchronized in the A1 Policy Management Service, and can seen in the Control Panel display when refreshed. )