You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "John Speidel (JIRA)" <ji...@apache.org> on 2014/03/25 16:48:16 UTC

[jira] [Created] (AMBARI-5206) proxy user settings need to be set when provisioning via a blueprint

John Speidel created AMBARI-5206:
------------------------------------

             Summary: proxy user settings need to be set when provisioning via a blueprint
                 Key: AMBARI-5206
                 URL: https://issues.apache.org/jira/browse/AMBARI-5206
             Project: Ambari
          Issue Type: Task
    Affects Versions: 1.5.0
            Reporter: John Speidel
            Assignee: John Speidel
             Fix For: 1.6.0


In core-site, there are a bunch of proxyuser settings.

These are in the form of :
hadoop.proxyuser.<username>.hosts
hadoop.proxyuser.<username>.groups

These are dynamically generated property names because they contain the user name in the property name.
These are currently not present in the stack definitions and are generated by the UI.

These are currently not being set when provisioning via a blueprint.

Until this is completed, users that deploy clusters that require proxy user properties will have to add them to the blueprint manually.
For example:
{code}
{
    "configurations" : [
        { 
            "core-site" : {
               "hadoop.proxyuser.oozie.hosts" : "*",
               "hadoop.proxyuser.oozie.groups" : "users" ,
               ...
            } 
        }
    ]
    ...
}   
{code} 

For more on cluster scoped blueprint configuration see:
https://issues.apache.org/jira/browse/AMBARI-5114




--
This message was sent by Atlassian JIRA
(v6.2#6252)