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

Hadoop QA commented on AMBARI-8657:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12687007/AMBARI-8657_02.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/920//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/920//console

This message is automatically generated.

> Add Kerberos Configuration Metadata File Builder and Reader
> -----------------------------------------------------------
>
>                 Key: AMBARI-8657
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8657
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: configurations, kerberos, security
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8657_01.patch, AMBARI-8657_02.patch
>
>
> Provide a facility to write (build) and read a (temporary) file used to hold 
> data needed for updating the configuration data of services to be configured 
> for Kerberos.
> The format of the file should be hidden from the user of this facility, but 
> will probably be CSV.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to