[
https://issues.apache.org/jira/browse/AMBARI-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019324#comment-16019324
]
tianbaochao commented on AMBARI-3524:
-------------------------------------
why did this issue not assigned for so long a time??
Is there no one had concern on this issue?
> 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: ambari-agent
> Reporter: Thibaut Marmin
> Labels: agent, cdh, cloudera, hdp, puppet, stack
>
> 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.3.15#6346)
