[ 
https://issues.apache.org/jira/browse/HADOOP-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839669#comment-16839669
 ] 

Eric Yang commented on HADOOP-16092:
------------------------------------

[~elek] you are miss-quoting me incorrectly.  My preference is to remove ozone 
from source tree naming.  This means there is no source repository prefix or 
suffix with ozone.  My message has always been the same, *build docker images 
inline*.  There is only one flag difference for existing developers to 
trigger/untrigger the docker build.  I never advocated for a separate source 
code repository for docker images, but ask you and the community to show me the 
release flow of using separate source code repository for docker image build.

As I predicted, the separate source code repository release model does not 
work.  We did not build and release hadoop-docker-ozone for Ozone 0.4.0 
release.  The docker-compose.yaml file must be updated with newer version and 
source getting voted on.  None of this had happened.  Once again, this has 
proven that separate source code repository for docker image build doesn't work 
while majority part of ozone source is in Hadoop repository.  The current 
implementation and ideas certainly did not come from me.

*It is possible to move Ozone code into Apache incubator and propose as a new 
incubation project to get a complete separation from Hadoop.  However, put on 
my Apache member hat that Ozone community has not grown to the point to 
function as an independent project at this time.*

Quote from [Marton own 
message|https://lists.apache.org/thread.html/ca3a8f37084b2562526384d8d7b2e647f4edc3c145a9dc41f04c23d7@%3Chdfs-dev.hadoop.apache.org%3E]:
  You insisted on separated branch or separate repository.  
You may have taken my message too literately with your own train of thoughts of 
keeping ozone versioning separate from Hadoop versioning.

My logic is trunk code will branch to ozone-0.4, and trunk moves to 
0.5.0-SNAPSHOT.  Docker images for 0.4.1 will released from ozone-0.4 branch 
because maven, docker and git are all tagged by the same version prefix.  
Hadoop can have its own docker module, and back ported to branch-2.x if we want 
to release 2.7.8 with a hadoop docker image.  That is a separate work item from 
Ozone.

Ozone versioning can remain separated from Hadoop versioning by ensuring that 
hadoop-ozone project has it's own set of 0.5.0-SNAPSHOT version in trunk.  In 
ozone-0.4 branch, the next version is 0.4.1-SNAPSHOT for building the inline 
docker image.  [~elek] does this address your concerns?



> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to