ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mugdha Varadkar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19044) Install & configure Ranger plugin components independently of Ranger admin components
Date Thu, 19 Jan 2017 10:24:26 GMT

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

Mugdha Varadkar updated AMBARI-19044:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Install & configure Ranger plugin components independently of Ranger admin components
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-19044
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19044
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: AMBARI-19044.1.patch, AMBARI-19044.1.trunk.patch, AMBARI-19044.2.patch,
AMBARI-19044.2.trunk.patch, AMBARI-19044.3.patch, AMBARI-19044.3.trunk.patch, AMBARI-19044-addendum-trunk.patch,
AMBARI-19044.patch, AMBARI-19044-ut-fix.patch
>
>
> Currently, Ambari provides a single toggle button to enable Ranger plugins for a component.
Plugin enabled results in a bunch of configuration which are created on backend which are
tighly coupled with Ranger admin installed on the same cluster.
> Need to make sure plugins communicate to Ranger admin which is installed on separate
cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message