| commit | d234bad707d39d442a64ae3f3c10c082b9bc2b16 | [log] [tgz] |
|---|---|---|
| author | Jessica Wagantall <jwagantall@linuxfoundation.org> | Wed Mar 21 10:38:42 2018 -0700 |
| committer | mmis <michael.morris@ericsson.com> | Thu Mar 29 10:35:43 2018 +0100 |
| tree | affa32b40b44c94f2e162b261b911d1a438dab35 | |
| parent | 1145b1ecb4efd211d1e7ff4376056cb1cc421bbb [diff] |
Update docker tag convention Update docker tagging script used by daily release builds: $VERSION-STAGING-YYYYMMDDTHHMMSSZ Change-Id: Ib3207f175fd41a8e90664bb1a139d4e0a3fcf259 Issue-ID: CIMAN-132 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
This source repository contains the files for building the ONAP Policy Engine Docker image policy-nexus.
To build it using Maven 3, first build 'policy/common', 'policy/engine', 'policy/drools-pdp', and 'policy/drools-applications' repositories, and then run: mvn prepare-package. This will pull the installation zip files needed for building the policy-pe and policy-drools Docker images into the target directory. It will not actually build the docker images; the following additional steps are needed to accomplish this:
To build the policy-nexus docker image, run the 'docker build' command on the following directory: policy-nexus
For example: docker build -t onap/policy-nexus policy-nexus
In addition, this source repository contains a docker-compose.yml file and associated configuration files (in the 'config' directory) that can be used to start up the ONAP Policy Engine docker containers
If you want to call the docker-compose, the following needs to be setup before doing so:
chmod +x config/drools/drools-tweaks.sh IP_ADDRESS=$(ifconfig eth0 | grep "inet addr" | tr -s ' ' | cut -d' ' -f3 | cut -d':' -f2) echo $IP_ADDRESS > config/pe/ip_addr.txt
If you do not want the policies pre-loaded, then set this environment variable to false:
export PRELOAD_POLICIES=false
It will override the settings in the .env file. Which is set to true.