[
https://issues.apache.org/jira/browse/AMBARI-18553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592372#comment-15592372
]
Hudson commented on AMBARI-18553:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #177 (See
[https://builds.apache.org/job/Ambari-branch-2.5/177/])
AMBARI-18553. Provision actions to happen based only on specified (smagyari:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a040cbfc549be03945f1e6b889fcbab16ad0c5f0])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewURLResourceProviderTest.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/metadata/RoleCommandOrderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/metadata/RoleCommandOrder.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stageplanner/RoleGraphFactory.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/stageplanner/TestStagePlanner.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ActiveWidgetLayoutResourceProviderTest.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/metadata/RoleCommandOrderProvider.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/CommandExecutionType.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/Stage.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserAuthorizationResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/metadata/RoleGraphTest.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterEffectiveVersionTest.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/metadata/RoleCommandPair.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackUpgradeConfigurationMergeTest.java
* (delete)
ambari-server/src/main/java/org/apache/ambari/server/stageplanner/RoleGraphFactoryImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stageplanner/RoleGraph.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/metadata/CachedRoleCommandOrderProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
> Provision actions to happen based only on specified dependencies
> ----------------------------------------------------------------
>
> Key: AMBARI-18553
> URL: https://issues.apache.org/jira/browse/AMBARI-18553
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-18553.patch, AMBARI-18553_v2.patch,
> AMBARI-18553_v3.patch, AMBARI-18553_v4.patch
>
>
> Today, the START commands stored in role_command_orders table are bound to
> multiple stages created based on dependencies between components - a
> component in the second stage can only begin its START after the entire first
> stage is done as opposed to just its dependencies in the first stage. This
> eventually increases the overall blueprint deployment time.
> This Jira tracks STARTing components just based on dependency order as
> specified by the role_command_order as opposed to the current stage based
> model.
> The goal is to be able to configure a direct dependency based execution model
> of commands, for now only for Blueprint based deployment commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
