You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Selvamohan Neethiraj (JIRA)" <ji...@apache.org> on 2016/04/26 00:12:12 UTC

[jira] [Updated] (RANGER-332) Ranger Plugin config to support policy manager URLs

     [ https://issues.apache.org/jira/browse/RANGER-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Selvamohan Neethiraj updated RANGER-332:
----------------------------------------
    Assignee:     (was: Selvamohan Neethiraj)

> 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
>             Fix For: 0.7.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
(v6.3.4#6332)