This page describes how to get and build the London release version of A1-Policy functions.
However, pre-built versions are available to download, so re-building is not necessary for the majority of users - and should only be attempted by experienced ONAP developers.
For more information on running the pre-built and tested versions see London - Run
Java 17 JDK (make sure that JAVA_HOME environment variable points to correct Java version)
Maven 3.8.3+
Docker and docker-compose (latest)
Download the ccsdk/oran
repo, london branch:
$ git clone "https://gerrit.onap.org/r/ccsdk/oran" -b london |
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.5.1-SNAPSHOT |
(Note: your version tag may be different - check the version in pom.xml
to make sure)
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 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.)
Project | Repo | Gerrit Link | Command | Note |
---|---|---|---|---|
CCSDK | ccsdk/parent | git clone "https://gerrit.onap.org/r/ccsdk/parent" -b london | mvn clean install -Dmaven.test.skip=true | If the parent artifacts are not yet released you need to build this repo in order to build other any other ccsdk repos (Including ccsdk/oran/a1-adapter ) |
CCSDK | ccsdk/features | git clone "https://gerrit.onap.org/r/ccsdk/features" -b london | mvn clean install -Dmaven.test.skip=true | |
CCSDK | ccsdk/distribution | git clone "https://gerrit.onap.org/r/ccsdk/distribution" -b london | mvn clean install -Dmaven.test.skip=true -Pdocker | Creates the CCSDK docker image |
SDNC | sdnc/northbound | git clone "https://gerrit.onap.org/r/sdnc/northbound" -b london | mvn clean install -Dmaven.test.skip=true | |
SDNC | sdnc/oam | git clone "https://gerrit.onap.org/r/sdnc/oam" -b london | mvn clean install -Dmaven.test.skip=true -Pdocker | Creates the SDNC docker image. Make sure you refer to the appropriate docker image version/tag in the pom.xml file, e.g., you may need to update ccsdk.docker.version for onap/ccsdk-ansible-server-image from 1.5.2-STAGING-latest to 1.5.2-SNAPSHOT-latest to refer to the latest newly built versions.(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 |
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:
CCSDK/distribution
repoprotocol://host:port
for example http://proxy:8443
CCSDK/distribution
components must be rebuilt, then SDNC/oam
repo must also be rebuilt to include the newly built CCSDK/distribution
components.