-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/49507/#review140346
-----------------------------------------------------------



Was this tested with the Storm Kerberos identity set to something like 
`storm1234@${realm}`?


ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py
 (line 303)
<https://reviews.apache.org/r/49507/#comment205733>

    Why are we hard-coding `{storm-user}-{cluster-name}` here?   If it is 
related to the Storm Kerberos identitiy, then there is no guarentee that the 
user won't change this when configuring Kerberos identities.


- Robert Levas


On July 1, 2016, 9:14 a.m., Gautam Borad wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/49507/
> -----------------------------------------------------------
> 
> (Updated July 1, 2016, 9:14 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Mugdha Varadkar, Robert 
> Levas, Sriharsha Chintalapani, Srimanth Gunturi, and Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-17520
>     https://issues.apache.org/jira/browse/AMBARI-17520
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Update the policy_user property in Advanced ranger-storm-plugin-properties of 
> Ranger with the value of the storm user bare principal specified in Storms 
> Ambari config.
> With this the principal used for storm will also be added to default ranger 
> policy and will prevent Storm service check failures.
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py
>  073bb1c 
>   
> ambari-server/src/main/resources/common-services/STORM/0.9.3/configuration/ranger-storm-plugin-properties.xml
>  2fee04f 
> 
> Diff: https://reviews.apache.org/r/49507/diff/
> 
> 
> Testing
> -------
> 
> Tested Ranger storm plugin on centos6 cluster. Kerberized the cluster and 
> checked that Storm service check is working fine.
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Reply via email to