[
https://issues.apache.org/jira/browse/RANGER-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bhavik patel updated RANGER-1481:
---------------------------------
Description:
In cloud setup scenario, shared data-lake cluster contains ranger admin service
and ephemeral clusters have ranger hive plugin that connect to ranger admin
service on remote data-lake cluster.
Ranger captures client/plugin ip in access and plugin audit info. As there are
multiple clusters in cloud environment, its difficult to map this ip to the
cluster it belongs to. Its useful to have the ambari cluster name in the access
and plugin audit info.
was:
In the HDC shared services setup, shared datalake cluster contains ranger admin
service and ephemeral clusters have ranger hive plugin that connect to ranger
admin service on remote datalake cluster.
Ranger captures client/plugin ip in access and plugin audit info. As there are
multiple clusters in cloud environment, its difficult to map this ip to the
cluster it belongs to. Its userful to have the ambari cluster name in the
access and plugin audit info.
> Capture cluster name in ranger audit info
> -----------------------------------------
>
> Key: RANGER-1481
> URL: https://issues.apache.org/jira/browse/RANGER-1481
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: bhavik patel
> Assignee: bhavik patel
> Fix For: 0.7.1
>
>
> In cloud setup scenario, shared data-lake cluster contains ranger admin
> service and ephemeral clusters have ranger hive plugin that connect to ranger
> admin service on remote data-lake cluster.
> Ranger captures client/plugin ip in access and plugin audit info. As there
> are multiple clusters in cloud environment, its difficult to map this ip to
> the cluster it belongs to. Its useful to have the ambari cluster name in the
> access and plugin audit info.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
