You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/06/11 18:27:00 UTC
[jira] [Commented] (HDDS-1635) Maintain docker entrypoint and
envtoconf inside ozone project
[ https://issues.apache.org/jira/browse/HDDS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861317#comment-16861317 ]
Hudson commented on HDDS-1635:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16724 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16724/])
HDDS-1635. Maintain docker entrypoint and envtoconf inside ozone project (aengineer: rev 3c9a5e7b16cb59fe48f660be3fb1fa3a140ad78a)
* (add) hadoop-ozone/dist/src/main/dockerbin/envtoconf.py
* (edit) hadoop-ozone/dist/dev-support/bin/dist-layout-stitching
* (add) hadoop-ozone/dist/src/main/dockerbin/entrypoint.sh
* (add) hadoop-ozone/dist/src/main/dockerbin/transformation.py
> Maintain docker entrypoint and envtoconf inside ozone project
> -------------------------------------------------------------
>
> Key: HDDS-1635
> URL: https://issues.apache.org/jira/browse/HDDS-1635
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.4.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> During an offline discussion with [~eyang] and [~arp], Eric suggested to maintain the source of the docker specific start images inside the main ozone branch (trunk) instead of the branch of the docker image.
> With this approach the ozone-runner image can be a very lightweight image and the entrypoint logic can be versioned together with the ozone itself.
> An other use case is a container creation script. Recently we [documented|https://cwiki.apache.org/confluence/display/HADOOP/Ozone+Docker+images] that hadoop-runner/ozone-runner/ozone images are not for production (for example because they contain development tools).
> We can create a helper tool (similar what Spark provides) to create Ozone container images from any production ready base image. But this tool requires the existence of the scripts inside the distribution.
> (ps: I think sooner or later the functionality of envtoconf.py can be added to the OzoneConfiguration java class and we can parse the configuration values directly from environment variables.
> In this patch I copied the required scripts to the ozone source tree and the new ozone-runner image (HDDS-1634) is designed to use it from this specific location.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org