----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/46263/#review129146 -----------------------------------------------------------
Ship it! Have you validated that TagSync installations in existing clusters still work after upgrading to this version of Ambari where it changes from a master to a slave? - Jonathan Hurley On April 15, 2016, 2:51 a.m., Mugdha Varadkar wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/46263/ > ----------------------------------------------------------- > > (Updated April 15, 2016, 2:51 a.m.) > > > Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Jonathan > Hurley, Jayush Luniya, Mahadev Konar, and Velmurugan Periasamy. > > > Bugs: AMBARI-15906 > https://issues.apache.org/jira/browse/AMBARI-15906 > > > Repository: ambari > > > Description > ------- > > 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. > > > Diffs > ----- > > > ambari-common/src/main/python/resource_management/libraries/functions/package_conditions.py > 4466671 > > ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/configuration/ranger-tagsync-site.xml > cfcab3b > > ambari-server/src/main/resources/stacks/HDP/2.5/services/RANGER/metainfo.xml > 9f96308 > ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > 7407da3 > > Diff: https://reviews.apache.org/r/46263/diff/ > > > Testing > ------- > > Tested on Centos 6 with and without RANGER_TAGSYNC. > > > Thanks, > > Mugdha Varadkar > >
