| commit | af657153239498810248a58b97c7edd8046cac7b | [log] [tgz] |
|---|---|---|
| author | liamfallon <liam.fallon@ericsson.com> | Wed Mar 14 21:39:28 2018 +0000 |
| committer | liamfallon <liam.fallon@ericsson.com> | Wed Mar 14 21:50:08 2018 +0000 |
| tree | 95d7ce3f2bf835e8a5ca841f4e7ed099a973bf01 | |
| parent | a4f7d7f89afa8296c892be8c906b23098aa7b0d0 [diff] |
Update oparent version to 1.1.0 Directive from ONAP project that all repos should be updated. Change vierified with a build with .m2 /org/onap cleared. Change-Id: Iec111c8442d219071339530a7ef891ff532928b9 Issue-ID: POLICY-693 Signed-off-by: liamfallon <liam.fallon@ericsson.com>
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/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.