This page describes how to get the Istanbul release version of A1-Policy functions up and running locally with two separate .

The A1-enabled Controller (SDNC with A1-Adapter) and A1 Policy Management Service will run in a local demonstrative deployment with four near-RT-RIC A1 simulator instances (docker containers providing ). These simulators will be configured to emulate devices implementing the "OSC_2.1.0" version of O-RAN A1 interface. (For more information on the OSC A1 Simulator functions see OSC NONRTRIC Wiki page (Release D))

All four components of these Non-RT RIC function run as docker containers and communicate via a private docker network. Details of the architecture can be found from Istanbul Release page.

Project Requirements

• 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)

...

• 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 anA1 Conrolelr fucntion an A1 Controller function (SDNC) existd 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 (see the step "Build A1 Controller" further below).

• 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.

...

Run A1-enabled Controller

To view use the A1 policy operations, Controller function (SDNC with A1-Adapter) you need to run the SDNC docker image. This image has few other docker image dependencies but not all are important for A1 policy testingfunctions. To bring up the sdnc container for A1 Policy Management testing a number of the not needed unneeded services can be removed from the docker compose file. (It is often difficult to get a full SDNC deployment up & running; removing unneeded components makes this easier)

Edit the docker compose file, oam/installation/src/main/yaml/docker-compose.yaml and keep only sdnc, maria db and ansible images. The rest of the images are not necessary for A1 Policy testing. However if you want to change the DG and run your own DG, you may need to keep the Directed Graph image.

...

(Note these instructions create an A1 Controller deployment scenario aligned towards the sample A1 Policy configuration given above)

If the steps above are unsuccessful more help can be found from the CCSDK/SDNC Developer teams: CCSDK Project & SDNC Project

Run OSC Near-RT-RIC/A1 Simulator Docker Containers

...