[
https://issues.apache.org/jira/browse/AMBARI-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729297#comment-15729297
]
Hadoop QA commented on AMBARI-18737:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842171/AMBARI-18737.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/9572//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9572//console
This message is automatically generated.
> Perf: Allow Kerberizing the PERF stack
> --------------------------------------
>
> Key: AMBARI-18737
> URL: https://issues.apache.org/jira/browse/AMBARI-18737
> Project: Ambari
> Issue Type: Story
> Components: ambari-agent
> Affects Versions: 2.5.0
> Reporter: Alejandro Fernandez
> Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-18737.patch
>
>
> Using multiple Ambari Agents per Host, each will need its unique
> /etc/security folder inside its home directory. In order to Kerberize the
> PERF stack, we will need to install an actual KDC and have the services
> actually kinit with their principals and keytabs.
> Because the PERF stack will not actually install any packages, it may have to
> create user accounts.
> The goal is to be able to run the Kerberos Wizard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
