Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

All components run as docker containers and communicate via a private docker network. Details of the architecture can be found from "New Delhi" Release page.

Note: Version numbers used in this page may not be the most recent ... you should verify the latest version numbers for released pre-built components in the docker image repository (https://nexus3.onap.org)

...

  • Copy the default configuration file oran/a1-policy-management/config/application_configuration.json (newdelhi) 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 here 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 values (in the name and baseUrl parameters for each ric entry) must match the given docker container names in near-RT-RIC simulator startup.
    Here the port is always port  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/SDNC.

    Info
    titleAlternative: Bypass 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:

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


...

ComponentRelease image and version tagStaging images and version tagManual snapshot (only available if manually built)
and version tag
A1 Policy Management Service

nexus3.onap.org:10002/onap/ccsdk-oran-a1policymanagementservice:1.7.1

nexus3.onap.org:10004/onap/ccsdk-oran-a1policymanagementservice:1.7.2-STAGING-latest

onap/ccsdk-oran-a1policymanagementservice:1.7.2-SNAPSHOT

SDNC imagenexus3.onap.org:10002/onap/sdnc-image:2.6.1nexus3.onap.org:10004/onap/sdnc-image:2.8.0-STAGING-latestonap/sdnc-image:2.8.0-SNAPSHOT

...