[
https://issues.apache.org/jira/browse/HDDS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704507#comment-16704507
]
Elek, Marton commented on HDDS-851:
-----------------------------------
I agree that we need a Dockerfile for in the repository to make it easier to
build ad-hoc docker builds. (See HDDS-872 which includes such a docker file).
However I think it's better to create a separated branch for creating the
official apache/ozone images:
1. The ASF release policy is very clear about distributing only the voted
releases. With registering the trunk branch as the source of the docker images
it could be not true. While it's possible to register only tags and not
branches. It will include and different build (not a big problem as the source
is the real release. But could be confusing)
2. With using the same branches it's harder to release versions. Let's imagine
the 0.4.0-alpha is voted and the released but the docker build is failed after
the final tagging. In this case the vote should be restarted.
3. It's also possible that we need to adjust the docker images for an older
release. For example in case of fixing something in the docker image /
hadoop-runner image we would have no other option just creating a new release.
With separating the docker image branches it's possible to update
apache/ozone:0.3.0-alpha docker image after the release.
[~anu] if you agree (and no more concern), can you please create a new
repository on the self-service page:
https://infra.apache.org/
> Provide official apache docker image for Ozone
> ----------------------------------------------
>
> Key: HDDS-851
> URL: https://issues.apache.org/jira/browse/HDDS-851
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Attachments: docker-ozone-latest.tar.gz, ozonedocker.png
>
>
> Similar to the apache/hadoop:2 and apache/hadoop:3 images I propose to
> provide apache/ozone docker images which includes the voted release binaries.
> The image can follow all the conventions from HADOOP-14898
> 1. BRANCHING
> I propose to create new docker branches:
> docker-ozone-0.3.0-alpha
> docker-ozone-latest
> And ask INFRA to register docker-ozone-(.*) in the dockerhub to create
> apache/ozone: images
> 2. RUNNING
> I propose to create a default runner script which starts om + scm + datanode
> + s3g all together. With this approach you can start a full ozone cluster as
> easy as
> {code}
> docker run -p 9878:9878 -p 9876:9876 -p 9874:9874 -d apache/ozone
> {code}
> That's all. This is an all-in-one docker image which is ready to try out.
> 3. RUNNING with compose
> I propose to include a default docker-compose + config file in the image. To
> start a multi-node pseudo cluster it will be enough to execute:
> {code}
> docker run apache/ozone cat docker-compose.yaml > docker-compose.yaml
> docker run apache/ozone cat docker-config > docker-config
> docker-compose up -d
> {code}
> That's all, and you have a multi-(pseudo)node ozone cluster which could be
> scaled up and down with ozone.
> 4. k8s
> Later we can also provide k8s resource files with the same approach:
> {code}
> docker run apache/ozone cat k8s.yaml | kubectl apply -f -
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
