ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15906) Make Ranger TagSync to be installed as a slave and optional
Date Tue, 19 Apr 2016 11:08:25 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247561#comment-15247561
] 

Hudson commented on AMBARI-15906:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4684 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4684/])
AMBARI-15906. Make Ranger TagSync to be installed as a slave and (gautam: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1faa5acd4102ac8299596445df7744ed26d34d0f])
* ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/metainfo.xml
* ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/configuration/ranger-tagsync-site.xml


> Make Ranger TagSync to be installed as a slave and optional
> -----------------------------------------------------------
>
>                 Key: AMBARI-15906
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15906
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Gautam Borad
>            Assignee: Mugdha Varadkar
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15906.1.patch, AMBARI-15906.patch
>
>
> In order to support blueprints to setup cluster without TagSync, make stack level changes
to allow Ranger TagSync to be installed as a optional slave component. 



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

Mime
View raw message