ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14555) Add Blueprints support for starting only a subset of components within a host group
Date Sat, 09 Jan 2016 06:30:39 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090455#comment-15090455
] 

Hudson commented on AMBARI-14555:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4140 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4140/])
AMBARI-14555. Add Blueprints support for starting only a subset of (rnettleton: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6d06814f729d45db11d63465d0e9d640c49d2b23])
* ambari-server/src/main/java/org/apache/ambari/server/topology/HostGroup.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterTopology.java
* ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog221Test.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ProvisionAction.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/RequiredPasswordValidator.java
* ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterTopologyImplTest.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintFactory.java
* ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorBlueprintProcessor.java
* ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog221.java
* ambari-server/src/test/java/org/apache/ambari/server/topology/BlueprintImplTest.java
* ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java
* ambari-server/src/main/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRenderer.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterTopologyImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/HostGroupImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/HostRequest.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ExportBlueprintRequestTest.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ProvisionClusterRequest.java
* ambari-server/src/test/java/org/apache/ambari/server/topology/RequiredPasswordValidatorTest.java
* ambari-server/src/test/java/org/apache/ambari/server/topology/BlueprintValidatorImplTest.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/LogicalRequest.java
* ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* ambari-server/src/test/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRendererTest.java
* ambari-server/src/test/java/org/apache/ambari/server/orm/entities/HostGroupComponentEntityTest.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostGroupComponentEntityPK.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java
* ambari-server/src/test/java/org/apache/ambari/server/topology/BlueprintFactoryTest.java
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintValidatorImpl.java
* ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostGroupComponentEntity.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ExportBlueprintRequest.java
* ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorBlueprintProcessorTest.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/Component.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintResourceProvider.java


> 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)

Mime
View raw message