[
https://issues.apache.org/jira/browse/AMBARI-15226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273423#comment-15273423
]
Tim Thorpe commented on AMBARI-15226:
-------------------------------------
I will reapply the patch over trunk tomorrow morning so that it is ready when
you get in. There were quite often changes with respect to the stack advisor
stuff but not often the java code.
> Custom services need a way to integrate in the stack advisor process
> --------------------------------------------------------------------
>
> Key: AMBARI-15226
> URL: https://issues.apache.org/jira/browse/AMBARI-15226
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Tim Thorpe
> Assignee: Tim Thorpe
> Fix For: trunk
>
> Attachments: AMBARI-15226.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the stack advisor is defined under each stack version such as
> HDP/2.3. The problem with this is that it restricts the services that can be
> added to the stack. If a custom service is to be added, they would need to
> modify the stack advisor. If configuration recommendations and validations
> could be done at the service level then a custom service could just include
> their own recommendations and validations separately.
> The idea here is that the stack advisor will continue to give the
> recommendations and validations for the core stack services but custom
> services would be able to provide their own service advisor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
