WORK IN PROGRESS

This page describes how to get and build the New Delhi release version of A1-Policy functions.

...

For more information on running the pre-built and tested versions see New Delhi - Run

Project Requirements

• Java 17 JDK (make sure that JAVA_HOME environment variable points to correct Java version)

• Maven 3.8.3+
  

• Docker and docker-compose (latest)

• Python

Build Code

• Note 1: While instructions to build the artifacts are included below, pre-built versions are available as Docker Images in http://nexus3.onap.org

  • Building the code should only be attempted if you really need to, or wish in incorporate some change; it is much easier to use the pre-built versions.

• Note 2: Before attempting to retrieve or build any ONAP component please follow the instructions for Setting Up Your Development Environment 

• Note 3: After re-building run the functions by following instructions at New Delhi - Run - but note the version numbers of the newly-built functions will likely be slightly different from the pre-built versions.

  • Version numbers used in this page may not be the most recent ... you should verify version numbers of your newly built component, and check for latest versions of pre-built components

Build A1 Policy Management Service container

• Download the ccsdk/oran repo, branch: newdelhi  newdelhi

  Code Block
  language bash
  $ git clone "https://gerrit.onap.org/r/ccsdk/oran" -b newdelhi

Build the code and create docker image

To build docker image of the A1 Policy Management Service:

$ cd oran/a1-policy-management/
$ mvn clean install -Dmaven.test.skip=true

If the build is successful an image with following name and tag shall be built, use the command 'docker images' to view the newly built image in the local docker registry.

(You should double check the docker tag/version corresponds to the version you've just built.)

$ docker images
onap/ccsdk-oran-a1policymanagementservice 1.7.03-SNAPSHOT

(Note: your version tag may be different - check the version in pom.xml to make sure)

Build A1 Adapter for SDNC Controller

Build the code and create docker images

A1 Adapter is a feature developed within CCSDK which can then be installed in the SDNC/ODL Karaf Server. To build & run the A1-enabled SDNC Controller, you need to build the CCSDK & SDNC repos.

The Controller provides a Northbound Interface, to be used only by the A1 Policy Management Service, allowing it to pass messages over the A1 interface to near-RT-RICs in the RAN.

Use the downloaded repo 'ccsdk/oran' as in the previous step, "Build A1 Policy Management Service container"

$ cd oran/a1-adapter/
$ mvn clean install -Dmaven.test.skip=true

After you build the A1 adapter artifacts, download below CCSDK/SDNC repos and build them in the following order.

(You should double check the docker tag/versions corresponds to the latest released versions and the version you've just built.)

Note: full re-builds of the CCSDK and SDNC projects are prone to errors - cloned functions may require manual tweaking to be successful. It is usually better to use pre-built and tested images.

If your build is unsuccessful more help can be found from the CCSDK/SDNC Developer teams: CCSDK Project & SDNC Project

If the builds are successful, images with following name and tag shall exist, use the command 'docker images' to view the newly built images in the local docker registry.

$ docker images | grep onap
onap/sdnc-image latest
onap/sdnc-ansible-server-image latest
onap/admportal-sdnc-image latest
onap/ccsdk-dgbuilder-image latest
onap/sdnc-ueb-listener-image latest
onap/sdnc-dmaap-listener-image:latest

Proxy support for A1 adapter

There is the possibility to use a HTTP proxy for A1 Adapter southbound calls (when CCSDK SLI graph node functions need to perform REST calls southbound to near-RT-RICs). 

To configure HTTP proxy:

• Add proxy URL to properties

  file 

  file odlsli/src/main/properties/a1-adapter-api-dg.properties

   variable 

   variable a1Mediator.proxy.url

  • This file is part of CCSDK/distribution repo

  • URL format must be protocol://host:port for example http://proxy:8443 

• After adding this information in the file, the CCSDK/distribution components must be rebuilt, then SDNC/oam repo must also be rebuilt to include the newly built CCSDK/distribution components.