ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nate Cole <nc...@hortonworks.com>
Subject Re: Review Request 41397: AMBARI-14383 Add support for Ranger TagSync process as a component under RANGER
Date Fri, 12 Feb 2016 16:24:33 GMT


> On Feb. 12, 2016, 9:28 a.m., Nate Cole wrote:
> > What's the status of this review?  If it's pushed, please close.  You can abort
the review if it's not going to happen.  Thanks.
> 
> Velmurugan Periasamy wrote:
>     Most likely, tagsync will need to be supported from 2.6 stack (this could change).
So my suggestion is to close this review and open a new one when the new patch is ready.

Sounds good.  I can't close it myself since I'm not the opener.


- Nate


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41397/#review119018
-----------------------------------------------------------


On Dec. 15, 2015, 11:46 a.m., Gautam Borad wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41397/
> -----------------------------------------------------------
> 
> (Updated Dec. 15, 2015, 11:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Madhan Neethiraj, Mahadev
Konar, Nate Cole, Sumit Mohanty, Selvamohan Neethiraj, and Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14383
>     https://issues.apache.org/jira/browse/AMBARI-14383
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Ranger TagSync is a separate component that will be responsible for synchronizing the
tags from Apache Atlas into Apache Ranger (db).
> 
> 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
> 
> 
> Diffs
> -----
> 
>   ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
fd83c53 
>   ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
5628f33 
>   ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
b6e5ee9 
>   ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
4f711c3 
>   ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
PRE-CREATION 
>   ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
8de0d80 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-tagsync-site.xml
PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/metainfo.xml 2fb8a9a

>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
cf3afbe 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml cce20be 
> 
> Diff: https://reviews.apache.org/r/41397/diff/
> 
> 
> Testing
> -------
> 
> Installed Ranger on centos 6 and enabled Ranger TagSync module.
> 
> Tested minor upgrade from 2.3.x to 2.3.xx
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message