ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8795) MAPREDUCE2 service components should indicate security state
Date Thu, 18 Dec 2014 16:00:15 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-8795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Levas updated AMBARI-8795:
---------------------------------
    Description: 
The MAPREDUCE2 service components should indicate security state when queried by Ambari Agent
via STATUS_COMMAND.  Each component should determine it's state as follows:

h3. HISTORYSERVER
h4. Indicators
* Command JSON
** config\['configurations']\['cluster-env']\['security_enabled'] 
*** = “true”
* Configuration File: params.hive_client_conf_dir + ‘mapred-site.xml’
** mapreduce.jobhistory.principal
*** not empty
*** required
** mapreduce.jobhistory.keytab
*** not empty
*** path exists and is readable
*** required
** mapreduce.jobhistory.webapp.spnego-principal
*** not empty
*** required
** mapreduce.jobhistory.webapp.spnego-keytab-file
*** not empty
*** path exists and is readable
*** required

h4. Pseudocode
{code}
if indicators imply security is on and validate
    if kinit(mapreduce.jobhistory.principal) succeeds
        state = SECURED_KERBEROS
    else
        state = ERROR 
else
    state = UNSECURED
{code}

_*Note*_: Due to the _cost_ of calling {{kinit}} results should be cached for a period of
time before retrying.  This may be an issue depending on the frequency of the heartbeat timeout.


  was:
The MAPREDUCE2 service components should indicate security state when queried by Ambari Agent
via STATUS_COMMAND.  Each component should determine it's state as follows:

h3. HISTORYSERVER
h4. Indicators
* Command JSON
** config\['configurations']\['cluster-env']\['security_enabled'] 
*** = “true”
* Configuration File: params.hive_client_conf_dir + ‘mapred-site.xml’
** mapreduce.jobhistory.principal
*** not empty
*** required
** mapreduce.jobhistory.keytab
*** not empty
*** path exists and is readable
*** required

h4. Pseudocode
{code}
if indicators imply security is on and validate
    if kinit(mapreduce.jobhistory.principal) succeeds
        state = SECURED_KERBEROS
    else
        state = ERROR 
else
    state = UNSECURED
{code}

_*Note*_: Due to the _cost_ of calling {{kinit}} results should be cached for a period of
time before retrying.  This may be an issue depending on the frequency of the heartbeat timeout.



> MAPREDUCE2 service components should indicate security state
> ------------------------------------------------------------
>
>                 Key: AMBARI-8795
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8795
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, stacks
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>             Fix For: 2.0.0
>
>
> The MAPREDUCE2 service components should indicate security state when queried by Ambari
Agent via STATUS_COMMAND.  Each component should determine it's state as follows:
> h3. HISTORYSERVER
> h4. Indicators
> * Command JSON
> ** config\['configurations']\['cluster-env']\['security_enabled'] 
> *** = “true”
> * Configuration File: params.hive_client_conf_dir + ‘mapred-site.xml’
> ** mapreduce.jobhistory.principal
> *** not empty
> *** required
> ** mapreduce.jobhistory.keytab
> *** not empty
> *** path exists and is readable
> *** required
> ** mapreduce.jobhistory.webapp.spnego-principal
> *** not empty
> *** required
> ** mapreduce.jobhistory.webapp.spnego-keytab-file
> *** not empty
> *** path exists and is readable
> *** required
> h4. Pseudocode
> {code}
> if indicators imply security is on and validate
>     if kinit(mapreduce.jobhistory.principal) succeeds
>         state = SECURED_KERBEROS
>     else
>         state = ERROR 
> else
>     state = UNSECURED
> {code}
> _*Note*_: Due to the _cost_ of calling {{kinit}} results should be cached for a period
of time before retrying.  This may be an issue depending on the frequency of the heartbeat
timeout.



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

Mime
View raw message