[
https://issues.apache.org/jira/browse/HDDS-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anu Engineer updated HDDS-1634:
-------------------------------
Resolution: Fixed
Fix Version/s: 0.4.1
Status: Resolved (was: Patch Available)
Just added a dummy fixed version, The branch does not have fixed versions
support yet. Thanks for the contribution, I have committed this to the feature
branch.
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.4.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
