ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9693) Review and update kerberos descriptors for various services
Date Wed, 18 Feb 2015 16:11:11 GMT

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

Hadoop QA commented on AMBARI-9693:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12699478/AMBARI-9693.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 1 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/1727//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1727//console

This message is automatically generated.

> Review and update kerberos descriptors for various services
> -----------------------------------------------------------
>
>                 Key: AMBARI-9693
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9693
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9693.patch
>
>
> In Ambari 1.7.0, UI used to make appropriate config property changes when kerberizing
the cluster.
> In 2.0.0, this is all driven by the Kerb API.
> But during testing we've noticed that some properties that were previously set were no
longer set. For example, hbase.hbase.coprocessor.master.classes, hbase.coprocessor.region.classes,
etc.
> See https://github.com/apache/ambari/blob/branch-1.7.0/ambari-web/app/data/HDP2/secure_mapping.js#L554
> There could be a bunch of other parameters that need to be ported over from the secure_mapping.js
file in order for the cluster to function properly in a secure manner.



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

Mime
View raw message