[
https://issues.apache.org/jira/browse/HADOOP-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851614#comment-16851614
]
Elek, Marton commented on HADOOP-16092:
---------------------------------------
Thanks to explain [~eyang] your opinion. I am sorry to say but I have slightly
different view.
bq. Hadoop-runner image is a distraction that serves no purpose to Hadoop
development.
I am afraid that is not quite true. It's heavily used by Ozone which is a
subproject of Hadoop.
bq. Fictional use case of having ability to run Hadoop 2.7.3 with latest
hadoop-runner image can not be supported in reality.
Sorry, but I wouldn't say fictional. I think it's a very valid use case to test
ozonefs with older released version (eg. for HDDS-1525).
bq. A new user may come in and said that he likes the hard coded uid, and
current hadoop-runner:latest breaks his backward compatibility
I am not sure If I understand this well. No uid has been changed in
hadoop-runner recently. Only the directory of configs/logs are changed and I
think it's still backward compatible with 0.3.0/0.4.0.
But I agree with you that it can be better to create more fixed tags from
hadoop-runner. This issue is about moving hadoop-runner to a separated
repository where we can easily create multiple tags with different
branches/tags if the right mapping is registered to the dockerhub.
bq. By bringing hadoop-runner docker build process into regular Hadoop
maintenance branches
We can't do this without refactoring the current way to use docker images in
ozone development. This is part of a separated, open discussion.
> Move the source of hadoop/ozone containers to the same repository
> -----------------------------------------------------------------
>
> Key: HADOOP-16092
> URL: https://issues.apache.org/jira/browse/HADOOP-16092
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Elek, Marton
> Assignee: Gabor Bota
> Priority: Major
>
> This is proposed by [~eyang] in
> [this|https://lists.apache.org/thread.html/33ac54bdeacb4beb023ebd452464603aaffa095bd104cb43c22f484e@%3Chdfs-dev.hadoop.apache.org%3E]
> mailing thread.
> bq. Hadoop community can decide what is best for Hadoop. My preference is to
> remove ozone from source tree naming, if Ozone is intended to be subproject
> of Hadoop for long period of time. This enables Hadoop community to host
> docker images for various subproject without having to check out several
> source tree to trigger a grand build
> As of now the source of hadoop docker images are stored in the hadoop git
> repository (docker-* branches) for hadoop and in hadoop-docker-ozone git
> repository for ozone (all branches).
> As it's discussed in HDDS-851 the biggest challenge to solve here is the
> mapping between git branches and dockerhub tags. It's not possible to use the
> captured part of a github branch.
> For example it's not possible to define a rule to build all the ozone-(.*)
> branches and use a tag $1 for it. Without this support we need to create a
> new mapping for all the releases manually (with the help of the INFRA).
> Note: HADOOP-16091 can solve this problem as it doesn't require branch
> mapping any more.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
