Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: POLICY-4287
Change-Id: I9c6c59e264624d35b70b26640c2442f937419527
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
Issue-ID: POLICY-4264
Signed-off-by: danielhanrahan <daniel.hanrahan@est.tech>
Change-Id: I8ab51f82a441361b8aa6b5f9aa0b6917ceea5399
|
|
Fix originally put in drools-pdp
Upgraded Python pip package as was causing build failure
Issue-ID: POLICY-3905
Change-Id: Ib5320790914a6a1344ae0548aeda3c7cf4585734
Signed-off-by: saul.gill <saul.gill@est.tech>
|
|
The onap-java image only installs the java jre, but policy needs the
jdk, thus we have been uninstalling the jre and then installing the jdk.
Unfortunately, this means that the policy-jdk image does not use the
latest ONAP-specified point release for either the java jdk OR python.
With this change, the policy-jdk image will start with the onap-python
image instead, thus python, at least will be up to date, even if the jdk
is not.
Note: tried using the latest adoptjdk image, but apparently there's
something different about that image that triggers a stack overflow in
apex-pdp. Consequently, we'll stay with the openjdk installed via
alpine "apk". This is still java 11, which satisfies ONAP requirements,
it just isn't the point release that is preferred.
Issue-ID: POLICY-3486
Change-Id: I0959c7048a38e30927b37b58deb887cc961a2150
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Modified the docker files to use the newer onap docker base image.
Issue-ID: POLICY-3390
Change-Id: Ia9b57d1909917225b22eea5920f91ad193655911
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Couldn't figure out a way to remove the jre, but was able to install the
jdk over top of it.
Issue-ID: POLICY-3134
Change-Id: I6096ff765500977f58449800192bbf2b53848efa
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
change to /bin/sh for policy user
Issue-ID: POLICY-2847
Change-Id: Ie2c88b3e15ab4ca2bf5e6d928f0f9c40c0688c4b
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
this gerrit would be the second step
to not to use any GPL-3.0 and plus license
Issue-ID: POLICY-2847
Change-Id: I637b8db2fd39a1f0864c8320b5744fc99350108c
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
Updated the docker images to alpine 3.12.0 so that a newer version of
openjdk11 would be pulled in.
Modified the jdk image to download maven via curl rather than installing
it via apk so-as to prevent it from installing java8 as a dependency.
Issue-ID: POLICY-2819
Change-Id: Iba4e2448b826ce6abb5df506228c99b9a3676495
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Various changes were made to the policy debian-slim docker
images. Made the same changes to the alpine images.
Issue-ID: POLICY-2374
Change-Id: I1acc6a7791dc7c4a9ba44ea2c70b19ebeb0acf94
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Change-Id: I9291f36e94d4b262cfe5bd0d420af86ce21205a8
Issue-ID: POLICY-2378
Signed-off-by: a.sreekumar <ajith.sreekumar@est.tech>
|
|
Split the RUN into separate items in an attempt to get past the
sporadic I/O Error when building the policy alpine docker images.
Updates per review comments:
- removed nss
- removed openssh (for now)
Issue-ID: POLICY-1586
Change-Id: I9e6181e67333a5fdf01c8a4286f117b673e50076
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Added debian-slim images based off of jre-slim.
Removed alpine images from the build.
If it's determined that we need a jdk instead of a jre, then
"jre" can be changed to "jdk" in the policy-base Dockerfile.
As an alternative, a new policy-docker-jdk image could be created,
based off of "jdk" and all of the apt packages added to it. In that
case, it would probably be appropriate to removed maven from the
packages that are loaded into the policy-common image.
Addressed first round of review comments:
- use specific version of java 11
- removed docker-maven-plugin version
- replaced the images with policy-jre-debian and policy-jdk-debian
- added a policy-jdk-alpine image, which includes the jdk & maven, but
is significantly smaller than the debian-slim version
- added a policy-jre-alpine image
Addressed additional review comments:
- removed BUILD_VERSION
- installed maven packages instead of downloading via curl
- added link to /usr/lib/jvm
Issue-ID: POLICY-1586
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: I43fd6a5c5ff9c4a0b537d3f297fdf2ad8248ba75
|