hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1634) Introduce a new ozone specific runner image
Date Tue, 11 Jun 2019 21:40:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1634?focusedWorklogId=258146&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-258146
]

ASF GitHub Bot logged work on HDDS-1634:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Jun/19 21:39
            Start Date: 11/Jun/19 21:39
    Worklog Time Spent: 10m 
      Work Description: elek commented on pull request #3: HDDS-1634. Introduce a new ozone
specific runner image
URL: https://github.com/apache/hadoop-docker-ozone/pull/3
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 258146)
    Time Spent: 0.5h  (was: 20m)

> 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
>          Time Spent: 0.5h
>  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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message