[
https://issues.apache.org/jira/browse/AMBARI-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226521#comment-14226521
]
John Speidel commented on AMBARI-6275:
--------------------------------------
An additional variation that I think that is very important is the ability to
add hosts without knowing the host names that are being added. We could allow
a count and an optional predicate to match appropriate hosts. We would look at
the registered hosts that were not associated with a cluster and match those to
the cluster creation request.
For example, assuming that all registered hosts are equal since we are not
specifying a host predicate:
{code}
POST clusters/c1/hosts
[
{
"blueprint_name" : "blueprint1",
"host_group" : "hostgroup_1",
"host_count" : 5
},
{
"blueprint_name" : "blueprint2",
"host_group" : "hostgroup_2",
"host_count" : 2
}
]
{code}
If there would be multiple "flavors" of registered hosts we would need a
mechanism to allow this to be specified in the request to ensure that the
correct hosts were associated with the correct host groups.
> Add support for "add hosts" with Blueprints API
> -----------------------------------------------
>
> Key: AMBARI-6275
> URL: https://issues.apache.org/jira/browse/AMBARI-6275
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Yusaku Sako
> Assignee: John Speidel
> Fix For: 2.0.0
>
>
> Support for "adding hosts" based on *blueprint* style *host_group* via Ambari
> REST API. There are two scenarios to consider for this JIRA:
> 1) Add hosts based on an existing host in the cluster (and it's *blueprint*
> style *host_group* component layout). This enables the user to add hosts with
> components similar to existing hosts in the cluster. For example: expand this
> cluster with these X hosts and make each of these hosts like Y host
> (components + configs) existing in the cluster.
> 2) Add hosts based on components + configs. This would be a verbose method
> that uses *blueprint* style *host_groups* and *configs* to allow you to add
> hosts to a cluster that do not necessarily have a component layout or config
> of a similar host existing in the cluster. For example: expand this cluster
> with these X hosts and make each of these hosts include Y components with Z
> configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
