[ https://issues.apache.org/jira/browse/AMBARI-17228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandor Magyari updated AMBARI-17228: ------------------------------------ Attachment: AMBARI-17228.patch > Blueprint deployments should support a "START_ONLY" provision_action for > clusters > --------------------------------------------------------------------------------- > > Key: AMBARI-17228 > URL: https://issues.apache.org/jira/browse/AMBARI-17228 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Robert Nettleton > Assignee: Sandor Magyari > Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-17228.patch > > > This JIRA tracks an extension to the work started in: > AMBARI-16220 > In that JIRA, support is being added to allow Blueprint deployments that skip > the installation steps, and only attempt to start all components in the > cluster after the configuration phase has completed. > In AMBARI-16220, the feature is configured via a property in > "ambari.properties", which configures this feature on the ambari-server > itself. > This current JIRA tracks a suggestion to extend this feature, such that the > "START_ONLY" mode can be treated as a new type of "provision_action". > Using the property specified in ambari.properties isn't incorrect, but may be > inconvenient in the future for enhancements and maintenance. > In multi-cluster scenarios, it might be better to configure this at the > cluster-level. > There has already been some work done to configure provisioning in a more > fine-grained way. > Sid's patch for the following Blueprints feature: > https://issues.apache.org/jira/browse/AMBARI-14283 > Shows how a "provision_action" can be selected for a given deployment. > This notion of a "provision_action" has also been extended to the component > level as well: > https://issues.apache.org/jira/browse/AMBARI-14555 > Currently, this "provision_action" configuration is only used to select an > INSTALL_ONLY deployment, but it could certainly be extended to have a > "START_ONLY" action as well. This would have the benefit of being able to > choose this option on a per-cluster basis, and not require an ambari-server > restart if this feature is desired but not enabled by default. > The following code reference shows how the "provision_action" configuration > option is used by a Blueprints deployment: > org.apache.ambari.server.topology.HostRequest#createTasks -- This message was sent by Atlassian JIRA (v6.3.4#6332)