You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Tim Thorpe (JIRA)" <ji...@apache.org> on 2016/02/29 17:49:18 UTC

[jira] [Updated] (AMBARI-15226) The stack advisor should be pushed down to the services

     [ https://issues.apache.org/jira/browse/AMBARI-15226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Thorpe updated AMBARI-15226:
--------------------------------
    Remaining Estimate: 0h  (was: 504h)
     Original Estimate: 0h  (was: 504h)

> The stack advisor should be pushed down to the services
> -------------------------------------------------------
>
>                 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
>
>   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 the configuration recommendation and validation can be done at the service level then the custom service could just include their own recommendations and validations separately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)