> On July 1, 2016, 9:45 a.m., Robert Levas wrote:
> > ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py,
> >  line 303
> > <https://reviews.apache.org/r/49507/diff/1/?file=1434910#file1434910line303>
> >
> >     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.
> 
> Velmurugan Periasamy wrote:
>     I think this is the standard format for storm values in Ambari kerberos 
> config. I will let Gautam confirm that.
> 
> Gautam Borad wrote:
>     The hard coding is in the form of {storm-user}-{cluster-name}, which is 
> the format for storm in Ambari.

This is a _default_ value suggested via the Kerberos descriptor in the stack, 
however a user may change this via the REST API or UI by updating the Kerberos 
descriptor cluster artifact (which contains the user changes to the stack 
version of the Kerberos Descriptor).  Therefore, I would not assume this 
pattern will always be the one used to build the Storm user/headless principal.


- Robert


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


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