[
https://issues.apache.org/jira/browse/HDDS-1635?focusedWorklogId=253737&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-253737
]
ASF GitHub Bot logged work on HDDS-1635:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jun/19 13:28
Start Date: 04/Jun/19 13:28
Worklog Time Spent: 10m
Work Description: elek commented on issue #894: HDDS-1635. Maintain
docker entrypoint and envtoconf inside ozone project
URL: https://github.com/apache/hadoop/pull/894#issuecomment-498671598
> ShellChecks?
Violations are fixed in the last commit.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 253737)
Time Spent: 1.5h (was: 1h 20m)
> 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
> Time Spent: 1.5h
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
