Modifing the your repos ，resources stacks of ambari-server，ambari-agent/puppet/modules/hdp/manifests/params.pp and server.pp of some components which you need may be OK.
At 2013-10-16 15:38:41,"Thibaut Marmin (JIRA)" <j...@apache.org> wrote: >Thibaut Marmin created AMBARI-3524: >-------------------------------------- > > Summary: Set up generic puppet module architecture to manage both > HDP and CDH (and Apache?) stacks > Key: AMBARI-3524 > URL: https://issues.apache.org/jira/browse/AMBARI-3524 > Project: Ambari > Issue Type: Improvement > Components: agent > Reporter: Thibaut Marmin > > >Currently ambari-agent manages stacks via puppet modules. These modules are >specific to HDP stacks in the sens that scripts strongly depend on it special >features: >- Some packages only exists in HDP stack (e.g. hadoop-sbin, hadoop-pipes, etc.) >- Some scripts doesn’t exists in CDH stack (e.g. >/usr/lib/hadoop/bin/hadoop-daemon.sh) >- Etc. > >To allow ambari to manage CDH stacks, two ways are possible according to my >point of view : >- Consider CDH services as new services. This includes development of new >puppet modules named cdh instead hdp. >- Make the current puppet modules more generic by removing all hdp references >in their names and develop an additional conditional level to handle cases as >you deploy CDH or HDP stack. > >The second method seems to be more attractive because it abstracts the tool >from HDP naming. > > > >-- >This message was sent by Atlassian JIRA >(v6.1#6144)
