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 Security State to Ambari database
Date Sat, 22 Nov 2014 00:11:33 GMT

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

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/12682973/AMBARI-8336_03.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/719//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/719//console

This message is automatically generated.

> Add Security 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, AMBARI-8336_03.patch
>
>
> In order to track which services and components have been or need to be secured, several
tables need to be updated with a {{security_state}} column to contain one the following values:
> * {{UNKNOWN}} - Indicates that it is not known whether the service or component is secured
or not
> * {{UNSECURED}} - Indicates service or component is not or should not be secured
> * {{SECURED_KERBEROS}} - Indicates component is or should be secured using Kerberos
> * {{SECURING}} - Indicates the component is in the process of being secured
> * {{UNSECURING}} - Indicates the component is in the process of being unsecured
> * {{ERROR}} - Indicates the component is not secured due to an error condition
> The following tables need to be updated:
> * hostcomponentdesiredstate - To indicate whether the component needs security added
or removed
> * hostcomponentstate - To indicate whether the component is currently configured for
security or not 
> * servicedesiredstate - To indicate whether the service (and it components) should or
should not be secured



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

Mime
View raw message