[
https://issues.apache.org/jira/browse/AMBARI-19044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825992#comment-15825992
]
Mugdha Varadkar commented on AMBARI-19044:
------------------------------------------
Committed to branch-2.5:
[7edd6df944b474183179d0432386a6015e6bc310|https://github.com/apache/ambari/commit/7edd6df944b474183179d0432386a6015e6bc310]
and trunk
[1524fd775d4b25d0896c648cb1bbc8ed3644a73d|https://github.com/apache/ambari/commit/1524fd775d4b25d0896c648cb1bbc8ed3644a73d]
> 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.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)
