You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "John Speidel (JIRA)" <ji...@apache.org> on 2015/05/20 22:48:59 UTC

[jira] [Resolved] (AMBARI-11266) Blueprint API: Move host_count and host_predicate fields up one level

     [ https://issues.apache.org/jira/browse/AMBARI-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Speidel resolved AMBARI-11266.
-----------------------------------
    Resolution: Fixed

merged to trunk

> Blueprint API: Move host_count and host_predicate fields up one level
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-11266
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11266
>             Project: Ambari
>          Issue Type: Task
>          Components: blueprints
>    Affects Versions: 2.1.0
>            Reporter: John Speidel
>            Assignee: John Speidel
>             Fix For: 2.1.0
>
>
> Recently, during 2.1 development, API additions were made that allow a host count and host predicate to be specified for blueprint provision and scaling requests.  
> The additions are documented in the Apache Jira: https://issues.apache.org/jira/browse/AMBARI-10750
> After some consideration and discussion, it has become clear that the host_count and host_predicate fields need to move up one level form their current location under hosts.  Only explicitly specified hosts will be contained within "hosts".
> For example:
> {code}
> {
>   "blueprint" : "bp1",
>   "host_groups" :[
>     { 
>       "name" : "master",  
>       "hosts" : [          
>         { 
>           "fqdn" : "john2.novalocal"
>         }
>       ]
>     },  
>     { 
>       "name" : "slave",   
>       "host_count" : "5",
>       "host_predicate" : "Hosts/cpu_count>1"   
>     }
>   ]
> }
> {code}



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