Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 6 Apr 2016 20:31:25 +0000 (UTC)
From: "Tim Thorpe (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12945517.1456764473000.154783.1459974685634@Atlassian.JIRA>
In-Reply-To: <JIRA.12945517.1456764473000@Atlassian.JIRA>
References: <JIRA.12945517.1456764473000@Atlassian.JIRA>
 <JIRA.12945517.1456764473780@arcas>
Subject: [jira] [Updated] (AMBARI-15226) Custom services need a way to
 integrate in the stack advisor process
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tim Thorpe updated AMBARI-15226:
--------------------------------
    Description: 
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.

  was: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.


> 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)