ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Thorpe (JIRA)" <>
Subject [jira] [Updated] (AMBARI-15226) Custom services need a way to integrate in the stack advisor process
Date Tue, 12 Apr 2016 17:29:25 GMT


Tim Thorpe updated AMBARI-15226:
    Attachment: AMBARI-15226.patch

Patch only handles custom components.  Currently HAWQ and PXF are treated as custom components.
 This means that their recommendations and validations have been moved from the
(HDP 2.3) into files (in their respective common-services folders).

> Custom services need a way to integrate in the stack advisor process
> --------------------------------------------------------------------
>                 Key: AMBARI-15226
>                 URL:
>             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

View raw message