Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 8 Jan 2016 22:01:39 +0000 (UTC)
From: "Robert Nettleton (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12927314.1452013269000.62047.1452290499873@Atlassian.JIRA>
In-Reply-To: <JIRA.12927314.1452013269000@Atlassian.JIRA>
References: <JIRA.12927314.1452013269000@Atlassian.JIRA>
 <JIRA.12927314.1452013269160@arcas>
Subject: [jira] [Updated] (AMBARI-14555) Add Blueprints support for starting
 only a subset of components within a host group
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Nettleton updated AMBARI-14555:
--------------------------------------
    Attachment: AMBARI-14555_branch_2.2.patch

Uploaded re-based patch for eventually merging this into branch-2.2.  The re-based version only required minor changes. 


> Add Blueprints support for starting only a subset of components within a host group
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-14555
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14555
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>             Fix For: 2.2.1
>
>         Attachments: AMBARI-14555.patch, AMBARI-14555_branch_2.2.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Currently, the Blueprint deployment process for a cluster will always take a component through the "INSTALL" and "START" phases.  
> While this is the correct default behavior for most cluster deployments, there are cases where a user would like more fine-grained control over when certain components are started. 
> There is currently some support for this, implemented by AMBARI-14283, however this support is currently cluster-wide, so that START commands can be disabled for the entire cluster, but not on a component-basis.
> I propose that we extend the work in AMBARI-14283 to also allow a Blueprint to specify that certain components may only use the "INSTALL" phase, and skip the "START" phase.  
> This work will require some minor additions to the Blueprint syntax, that I'll publish in this proposal.  
> The Blueprint syntax should support marking each comopnent as having a "provision_action" that can override the default "INSTALL_AND_START" behavior.  


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