[jira] [Commented] (AMBARI-10750) Initial Implementation of Advanced API Cluster Provisioning Functionality

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

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

Hadoop QA commented on AMBARI-10750:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12728195/AMBARI-10750.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 21 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 test build failed in ambari-server 

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

This message is automatically generated.

> Initial Implementation of Advanced API Cluster Provisioning Functionality
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-10750
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10750
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server, blueprints
>    Affects Versions: Ambari-2.1
>            Reporter: John Speidel
>            Assignee: John Speidel
>             Fix For: Ambari-2.1
>
>         Attachments: AMBARI-10750.patch
>
>
> API based (blueprint) cluster provisioning modifications and enhancements which will provide for more flexible, scalable and robust cluster provisioning.
> This will include API and backend changes.
> - Allow a host count to be specified in the cluster creation template instead of host names.  This is documented in https://issues.apache.org/jira/browse/AMBARI-6275
> - Allow cluster creation or scaling to be started via the REST API prior to all/any hosts being available.  As hosts register with Ambari server they will be matched to request host groups and provisioned according to the requested topology
> - Allow host predicates to be specified along with host count to provide more flexibility in matching hosts to host groups.  This will allow for host flavors where different host groups are matched to different host flavors
> - Break up the current monolithic provisioning request into a request for each host operation.  For example, install on host A, start on host A, install on hostB, etc.  This will allow hosts to make progress even when another host encounters a failure.
> This Jira will be updated shortly with more information on this extensive set of enhancements and changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)