Robert Nettleton created AMBARI-14555:
-----------------------------------------
Summary: 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
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)
