[
https://issues.apache.org/jira/browse/HDDS-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584148#comment-16584148
]
Hudson commented on HDDS-218:
-----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14794 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14794/])
HDDS-218. add existing docker-compose files to the ozone release (xyao: rev
9dd5d5ba713240c559b102fa3172b10077f5da87)
* (edit) hadoop-dist/src/main/compose/ozone/docker-compose.yaml
* (edit) hadoop-ozone/docs/content/GettingStarted.md
* (edit) hadoop-dist/pom.xml
* (add) hadoop-dist/src/main/compose/README.md
* (edit) dev-support/bin/ozone-dist-layout-stitching
* (edit) hadoop-dist/src/main/compose/ozoneperf/docker-compose.yaml
> add existing docker-compose files to the ozone release artifact
> ---------------------------------------------------------------
>
> Key: HDDS-218
> URL: https://issues.apache.org/jira/browse/HDDS-218
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Minor
> Labels: newbie
> Fix For: 0.2.1
>
> Attachments: HDDS-218.001.patch, HDDS-218.002.patch
>
>
> Currently we use docker-compose files to run ozone pseudo cluster locally.
> After a full build, they can be found under hadoop-dist/target/compose.
> As they are very useful, I propose to make them part of the ozone release to
> make it easier to try out ozone locally.
> I propose to create a new folder (docker/) in the ozone.tar.gz which contains
> all the docker-compose subdirectories + some basic README how they could be
> used.
> We should explain in the README that the docker-compose files are not for
> production just for local experiments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
