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-8336) Add Kerberos State to Ambari database
Date Mon, 17 Nov 2014 21:47:34 GMT

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

Hadoop QA commented on AMBARI-8336:
-----------------------------------

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

This message is automatically generated.

> Add Kerberos State to Ambari database
> -------------------------------------
>
>                 Key: AMBARI-8336
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8336
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: kerberos
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8336_01.patch, AMBARI-8336_02.patch
>
>
> In order to track which services and components have been or need to be _Kerberized_
several tables need to be updated with a {{kerberos_state}} column to contain one the following
values:
> * {{UNKNOWN}} - Indicates the state is unknown
> * {{OFF}} - Indicates the service or component is not or should not be Kerberized
> * {{ON}} - Indicates the service or component is or should be Kerberized
> * {{IN_PROGRESS}} - Indicates the component is in the process of being Kerberized 
> * {{ERROR}} - Indicates the component cannot or failed to be Kerberized
> The following tables need to be updated:
> * hostcomponentdesiredstate - To indicate whether the component needs Kerberos added
or removed ({{OFF}}, {{ON}})
> * hostcomponentstate - To indicate whether the component is currently configured for
Kerberos or not ({{OFF}}, {{IN_PROGRESS}}, {{ON}}, {{ERROR}}, {{UNKNOWN}})
> * servicedesiredstate - To indicate whether the service (and it components) should or
should not be Kerberized ({{OFF}}, {{ON}})



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

Mime
View raw message