[
https://issues.apache.org/jira/browse/RANGER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-332:
-----------------------------------
Fix Version/s: 2.1.0
> Ranger Plugin config to support policy manager URLs
> ---------------------------------------------------
>
> Key: RANGER-332
> URL: https://issues.apache.org/jira/browse/RANGER-332
> Project: Ranger
> Issue Type: Bug
> Components: plugins
> Affects Versions: 0.5.0
> Reporter: Dilli Arumugam
> Priority: Major
> Fix For: 2.1.0
>
>
> During discussions on 03/19/15 about Ranger HA, an idea of supporting
> multiple instances of Ranger without load balancer was touched upon. To
> support this, agent plugins should have the smartness to be aware of multiple
> ranger admin end points and should have the smartness to failover to a
> functional ranger admin endpoint.
> CURRENT DESIGN:
> The plugin retrieves the policy from RangerAdmin via authenticated REST API
> call. When you have more than one ranger-admin, current design expects a
> load-balancer url to cover all of the ranger-admin web application.
> PROPOSED HIGH-LEVEL DESIGN:
> If the end-user decides to use multiple ranger-admin web application without
> having a load balancer, the end-user needs to configure the plugins to use
> list of ranger-admin url and the plugins should be modified to do a smart
> lookup across all url to find an active url to retrieve the policies.
> MODIFICATION NEEDED:
> plugin code that retrieve policies
> usersync code that retrieve & update user/group information
> any other external REST API consumers
> Please provide your comments and/or alternatives to this approach.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
