ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18737) Perf: Allow Kerberizing the PERF stack
Date Wed, 07 Dec 2016 17:45:58 GMT


Hadoop QA commented on AMBARI-18737:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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
                        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:
Console output:

This message is automatically generated.

> Perf: Allow Kerberizing the PERF stack
> --------------------------------------
>                 Key: AMBARI-18737
>                 URL:
>             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, AMBARI-18737_2.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

View raw message