[
https://issues.apache.org/jira/browse/AMBARI-19044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827584#comment-15827584
]
Hudson commented on AMBARI-19044:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #747 (See
[https://builds.apache.org/job/Ambari-branch-2.5/747/])
AMBARI-19044 Install & configure Ranger plugin components independently
(mugdha:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=93a0d939aa881eedd25550e48c379267abd17e6b])
* (edit) ambari-server/src/test/python/stacks/2.0.6/configs/nn_eu.json
> 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, 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)
