[
https://issues.apache.org/jira/browse/HDDS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839991#comment-16839991
]
Eric Yang commented on HDDS-1495:
---------------------------------
{quote}The current approach allows us to build the docker images independent of
the code base, allows management by Apache Infra, but allows the flexibility
for us to check-in and build/publish apache Images at will.\{quote}
I disagree. I shouldn't have to find out that we made a release vote on Ozone
0.4.0 then to find out that the blockade test is testing on
apache/hadoop-runner:latest docker image instead of apache/ozone:0.4.0 release.
This arrangement completely breaks the Apache release voting process because
it allows someone to make changes to hadoop-runner docker image to change the
definition of Ozone 0.4.0 release on Docker hub.
{quote}I am well aware of that, it was a lot of entertainment to read those
emails. Let us not drag ozone into that for now; at least until we have GA
release. We have more high priority items to deal with now.\{quote}
The release process must be inline with Apache release process. You can
generate the source tarball from hadoop-docker-ozone, and also the docker save
command to ensure the missing code are voted on. Without doing the proper
packaging of hadoop-docker-ozone and docker-compose file version tagging, it is
hollow to vote on any Ozone releases. The binary that runs from Ozone release
tarball can differ from day to day depending on what is uploaded in
apache/hadoop-runner. The current approach can not be claimed as working
because the community hasn't been able to follow through its own release
process design, and breaks Apache release voting process. If Ozone community
does not follow through then I would have no choice but withdrew my own vote
for Ozone 0.4.0 release.
> Create hadoop/ozone docker images with inline build process
> -----------------------------------------------------------
>
> Key: HDDS-1495
> URL: https://issues.apache.org/jira/browse/HDDS-1495
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Eric Yang
> Priority: Major
> Attachments: HADOOP-16091.001.patch, HADOOP-16091.002.patch,
> HDDS-1495.003.patch, HDDS-1495.004.patch, HDDS-1495.005.patch,
> HDDS-1495.006.patch, HDDS-1495.007.patch, Hadoop Docker Image inline build
> process.pdf
>
>
> This is proposed by [~eyang] in
> [this|https://lists.apache.org/thread.html/33ac54bdeacb4beb023ebd452464603aaffa095bd104cb43c22f484e@%3Chdfs-dev.hadoop.apache.org%3E]
> mailing thread.
> {quote}1, 3. There are 38 Apache projects hosting docker images on Docker hub
> using Apache Organization. By browsing Apache github mirror. There are only 7
> projects using a separate repository for docker image build. Popular projects
> official images are not from Apache organization, such as zookeeper, tomcat,
> httpd. We may not disrupt what other Apache projects are doing, but it looks
> like inline build process is widely employed by majority of projects such as
> Nifi, Brooklyn, thrift, karaf, syncope and others. The situation seems a bit
> chaotic for Apache as a whole. However, 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. However,
> inline build process seems more popular than separated process. Hence, I
> highly recommend making docker build inline if possible.
> {quote}
> The main challenges are also discussed in the thread:
> {code:java}
> 3. Technically it would be possible to add the Dockerfile to the source
> tree and publish the docker image together with the release by the
> release manager but it's also problematic:
> {code}
> a) there is no easy way to stage the images for the vote
> c) it couldn't be flagged as automated on dockerhub
> d) It couldn't support the critical updates.
> * Updating existing images (for example in case of an ssl bug, rebuild
> all the existing images with exactly the same payload but updated base
> image/os environment)
> * Creating image for older releases (We would like to provide images,
> for hadoop 2.6/2.7/2.7/2.8/2.9. Especially for doing automatic testing
> with different versions).
> {code:java}
> {code}
> The a) can be solved (as [~eyang] suggested) with using a personal docker
> image during the vote and publish it to the dockerhub after the vote (in case
> the permission can be set by the INFRA)
> Note: based on LEGAL-270 and linked discussion both approaches (inline build
> process / external build process) are compatible with the apache release.
> Note: HDDS-851 and HADOOP-14898 contains more information about these
> problems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
