[ 
https://issues.apache.org/jira/browse/HDDS-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607698#comment-16607698
 ] 

Hadoop QA commented on HDDS-411:
--------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} 
| {color:red} HDDS-411 does not apply to trunk. Rebase required? Wrong Branch? 
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDDS-411 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12938902/HDDS-411.001.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1008/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Add Ozone submodule to the hadoop.apache.org
> --------------------------------------------
>
>                 Key: HDDS-411
>                 URL: https://issues.apache.org/jira/browse/HDDS-411
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Dinesh Chitlangia
>            Priority: Trivial
>              Labels: site
>         Attachments: HDDS-411.001.patch
>
>
> The current hadoop.apache.org doesn't mention Ozone in the "Modules" section.
> We can add something like this (or better):
> {quote}
> Hadoop Ozone is an object store for Hadoop on top of the Hadoop HDDS which 
> provides low-level binary storage layer.
> {quote}
> We can also linke to the http://ozone.hadoop.apache.org



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to