[jira] [Commented] (AMBARI-18553) Provision actions to happen based only on specified dependencies

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-18553:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12832189/AMBARI-18553.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 10 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.controller.internal.UserResourceProviderTest
                  org.apache.ambari.server.controller.internal.ActiveWidgetLayoutResourceProviderTest
                  org.apache.ambari.server.controller.internal.UserAuthorizationResourceProviderTest

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/8828//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8828//console

This message is automatically generated.

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