-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove AdoptJDK as workaround if Sentinel-3 images are upgraded #578
Comments
@w-fsi You can have a look on F1:
The CFI are pushed on F2 and ready to integrated::
This images shall be incorporated on RS. I propose to use this US for incorporation in the next delivery. Do you agree ? Moreover, we are interested in deploying and testing its quickly on production. If the updates don't impact the RS Add-on configuration, I would like to deploy the develop version of the execution-workers as soon as possible. Note: We are still waiting for new Centos 7 images. Other updates may be added to the next delivery. I don't have any visibility. |
We updated the container and chains on the develop-branch for the SR1 and MW1 chains. The workaround was removed for these IPF-containers. The dynamic libraries and java 11 were successfully found and there were no additional changes in the task tables. |
Here below the last images to update:
|
@Woljtek |
I fixed OL1-RAC. |
All mentioned IPFs was upgraded and OpenJDK removed. |
Delivered in Sentinel-3 v1.14.0 (https://github.com/COPRS/processing-sentinel-3/releases) and in Production Common v1.14.0 (refer to https://github.com/COPRS/production-common/releases) |
SYS_CCB_w29 : All Sentinel-3 execution worker images have been provided with Centos 7 Operating System. This ticket can be closed. |
For information, the US includes only L1 and L2. The updates of L0 is handled:
|
User story description: _"As a [COPRS integrator] I need at least Java 11 in order to operate the IPF Execution Worker. However the S3 images are currently based on Centos 6 and it is not possible to retrieve a recent version from the official repositories.
Thus it was decided to use another binary java distribution as a workaround. AdoptJDK is currently pulled into the image:
RUN wget https://github.com/adoptium/temurin11-binaries/releases/download/jdk-11.0.16.1%2B1/OpenJDK11U-jdk_x64_linux_hotspot_11.0.16.1_1.tar.gz RUN tar -xf OpenJDK11U-jdk_x64_linux_hotspot_11.0.16.1_1.tar.gz && rm OpenJDK11U-jdk_x64_linux_hotspot_11.0.16.1_1.tar.gz
And a workaround is added to the start script of the execution worker in order to inject the Java Home via an environmental variable:
# Install java 11 - workaround for AdoptJDK RUN sed -i '1 a\export PATH=$PATH:/opt/jdk-11.0.16.1+1/bin' /app/start.sh
These modifications shall be removed once ESA providing a base image based on a more recent Centos version able to retrieve a suitable JVM from the official repositories.
"_
Acceptance criteria:
Definition of Done The User Story is considered completed when...
The text was updated successfully, but these errors were encountered: