ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14383) Add support for Ranger TagSync process as a component under RANGER
Date Thu, 07 Apr 2016 13:45:25 GMT

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

Andrew Onischuk commented on AMBARI-14383:
------------------------------------------

+1 as this is big patch and hand to merge.
But please create a separate jira to add show_logs, on start/stop failures, as we do for other
components, this would be a pretty useful thing in debugging failures.

Also just one more change
{noformat}
+  if os.path.isfile(tagsync_services_file):
+    File(tagsync_services_file,
+      mode = 0755,
+    )
+    Execute(('ln','-sf', format('{tagsync_services_file}'),'/usr/bin/ranger-tagsync'),
+      not_if=format("ls /usr/bin/ranger-tagsync"),
+      only_if=format("ls {tagsync_services_file}"),
+      sudo=True)
{noformat}
That if seems weird as in case someone changes permissions to 000 let's say, we won't change
it back. Can we remove it?

> Add support for Ranger TagSync process as a component under RANGER
> ------------------------------------------------------------------
>
>                 Key: AMBARI-14383
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14383
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-14383.1.patch, AMBARI-14383.2.patch, AMBARI-14383.3.patch,
AMBARI-14383.patch
>
>
> Ranger TagSync is a separate service that will be responsible for synchronizing the tags
from Apache Atlas into Apache Ranger (db).
> This jira will track changes required to install/configure TagSync from Ambari.
> * Add Ranger TagSync component under existing RANGER service. 
> * The component will be a master component
> * Ability to start/stop the component independently of Ranger Admin.
> * Ability to install the component on any host of the cluster
> * Support should be available only from HDP 2.3
> * Any other changes required in Ambari stack to support such component



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

Mime
View raw message