[ https://issues.apache.org/jira/browse/AMBARI-23864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vishal Suvagia resolved AMBARI-23864. ------------------------------------- Resolution: Fixed committed to [trunk|https://github.com/apache/ambari/commit/e2ce601032d2dd1f047793aa51d749749017774b]. > Need to add new property for Ranger-Tagsync when enabling federation for > Namenode-HA via Blueprints > --------------------------------------------------------------------------------------------------- > > Key: AMBARI-23864 > URL: https://issues.apache.org/jira/browse/AMBARI-23864 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.7.0 > Reporter: Vishal Suvagia > Assignee: Vishal Suvagia > Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Need to dynamically add properties in config-type {{ranger-tagsync-site}} > when cluster is being setup via blueprint . This should be done when Atlas > and Ranger-Tagsync service is installed. > When federation is Enabled for HDFS, in this case for each name-service, we > will need to add a property in config-type {{ranger-tagsync-site}} using > below format: > {noformat}ranger.tagsync.atlas.hdfs.instance.<cluster-name>.nameservice.<name-service>.ranger.service= > <ranger service-name>{noformat} > The Ranger service name can be derived from logic as below: > If the value for property {{ranger.plugin.hdfs.service.name}} is default i.e. > {{{{repo_name}}}} then the value for above property will be in the format: > {noformat}<cluster-name>_hadoop_<name-service>{noformat} > for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}} > , {{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value > {{{{repo_name}}}} then the property-value will be as below: > ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=testcl1_hadoop_ns1 > ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=testcl1_hadoop_ns2 > If the user has a custom-value for the property > {{ranger.plugin.hdfs.service.name}} i.e. not {{{{repo_name}}}}, then we will > need to use the value provided in for property > {{ranger.plugin.hdfs.service.name}} and use the format as > <custom-repo-name>_<name-service>. > for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}} > , {{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value > {{hadoop_service}} then the property-value will be as below: > ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=hadoop_service_ns1 > ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=hadoop_service_ns2 > PS : Related NN-Federation UI-wizard changes are already handled in > AMBARI-23424, This issue is created to handle addition of properties via > blueprint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)