Return-Path: X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2736919E8C for ; Fri, 29 Apr 2016 20:12:13 +0000 (UTC) Received: (qmail 59956 invoked by uid 500); 29 Apr 2016 20:12:13 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 59910 invoked by uid 500); 29 Apr 2016 20:12:13 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 59894 invoked by uid 99); 29 Apr 2016 20:12:12 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Apr 2016 20:12:12 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DB0E52C14F4 for ; Fri, 29 Apr 2016 20:12:12 +0000 (UTC) Date: Fri, 29 Apr 2016 20:12:12 +0000 (UTC) From: "Tim Thorpe (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-15226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-15226: -------------------------------- Status: Open (was: Patch Available) > 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 > > 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)