Aleksandr Kovalenko created AMBARI-23424:
--------------------------------------------

             Summary: Need to add new property for Ranger-Tagsync when enabling 
federation for Namenode-HA via UI wizard
                 Key: AMBARI-23424
                 URL: https://issues.apache.org/jira/browse/AMBARI-23424
             Project: Ambari
          Issue Type: Bug
          Components: ambari-web
    Affects Versions: 2.7.0
            Reporter: Aleksandr Kovalenko
            Assignee: Aleksandr Kovalenko
             Fix For: 2.7.0


Need to dynamically add properties in config-type {{ranger-tagsync-site}} from 
UI for Federation wizard. 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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to