Page Comparison

This page describes how to get the Istanbul release version of A1-Policy functions up and running using Docker.

...

• Copy the default configuration file oran/a1-policy-management/config/application_configuration.json (Jakarta) to the current directory, 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. See the step "Run OSC Near-RT-RIC/A1 Simulator Docker Containers" below)

• The controller URL (hostname, port), username and password values to access the A1 Controller (SDNC + A1 Adapter) must match the values configured for the SDNC-A1-Controller. (See the step "Run A1 Controller" further below). The port number 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 entry) 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 (SDNC + A1 Adapter) if desired - 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
  If all configured rics bypass the A1-Controller (do not have "controller" values) then the "controller" object at the top of the configuration can be omitted.
  If all configured rics bypass the A1-Controller there is no need to start an A1-Controller.
  

  Info
  title Optional: Do not connect through SDNC / A1 AdapterBypass the A1-Controller - connect direct from A1-Policy Management Service
  There is no functional gain in accessing the near-RT-RIC through an A1-Controller. To bypass the  A1-Controller (SDNC + A1 Adapter), where the A1-Policy Management Service connects directly to the A1 Interface: If all configured rics bypass the A1-Controller (do not have "controller" values) then the "controller" object at the top of the configuration can be omitted. If all configured rics bypass the A1-Controller there is no need to start an A1-Controller. Expand title Sample application configuration - bypassing the A1-Controller (SDNC & A1-Adapter) Code Block language yml title Sample Application Configuration - bypassing the A1-Controller linenumbers true collapse true {  "description": "Application configuration", "config": { "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/",        "managedElementIds": [ "kista_5", "kista_6" ] }, { "name": "ric4", "baseUrl": "http://ric4:8085/",       "managedElementIds": [ "kista_7", "kista_8", "kista_9", "kista_10", "kista_11"        ] } ] } }

  
  

...

...