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

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0
• Labels: blueprints
• Assignee: John Speidel
• Reporter: John Speidel
• Created: 25/Mar/14 15:47
• Updated: 26/Mar/14 18:34
• Resolved: 26/Mar/14 18:34

Description

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:

{
    "configurations" : [
        { 
            "core-site" : {
               "hadoop.proxyuser.oozie.hosts" : "*",
               "hadoop.proxyuser.oozie.groups" : "users" ,
               ...
            } 
        }
    ]
    ...
}   

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

Issue Links

• links to: ReviewBoard