[
https://issues.apache.org/jira/browse/HDFS-12469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDFS-12469:
--------------------------------
Attachment: HDFS-12469-HDFS-7240.WIP1.patch
Work in progress patch. Not for merge, yet.
I adjusted the base image as originally I created this with a more simple
baseimage (for example KSM/SCM started with root user in the container, but now
it has been changed).
TODO items (will be fixed soon):
1. Test it on OSX (I tested it on linux)
2. Adjust the configuration (some settings contains localhost, should be fixed)
3. Add documentation. I am wondering which one is the better: extend the
GettingStarted guide or write a separated one.
4. Try out the commands from the GettingStartedGuide + Corona run
If you would like to test it now, you can
{code}
cd dev-support/compose/ozone
docker-compose up -d
{code}
And check the namenode: 0.0.0.0:9870
> Ozone: Create docker-compose definition to easily test real clusters
> --------------------------------------------------------------------
>
> Key: HDFS-12469
> URL: https://issues.apache.org/jira/browse/HDFS-12469
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Fix For: HDFS-7240
>
> Attachments: HDFS-12469-HDFS-7240.WIP1.patch
>
>
> The goal here is to create a docker-compose definition for ozone
> pseudo-cluster with docker (one component per container).
> Ideally after a full build the ozone cluster could be started easily with
> after a simple docker-compose up command.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
