Elek, Marton created HDDS-851:
---------------------------------
Summary: 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
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: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
