You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2019/06/03 10:44:00 UTC
[jira] [Created] (HDDS-1634) Introduce a new ozone specific runner
image
Elek, Marton created HDDS-1634:
----------------------------------
Summary: Introduce a new ozone specific runner image
Key: HDDS-1634
URL: https://issues.apache.org/jira/browse/HDDS-1634
Project: Hadoop Distributed Data Store
Issue Type: Improvement
Reporter: Elek, Marton
Assignee: Elek, Marton
Ozone compose files use apache/hadoop-runner to provide a fixed environment to run any Ozone distribution.
It can be better to use separated hadoop-runner and ozone-runner:
1. To make it easier to include Ozone specific behaviour (For example goofys install, scm/om initialization)
2. To make it clean which feature is required by all the subprojects of Hadoop and which one is Ozone specific (base on the comment from [~eyang] in HADOOP-16092)
3. for hadoop-runner we maintain two tags (jdk11/jdk8/latest). And it seems to be hard to maintain all of them. jdk8 is required only for hadoop and with separating hadoop-runner/ozone-runner we can use only one simple branch for ozone-runner development (and we can create incremental fixed tags very easily)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org