[
https://issues.apache.org/jira/browse/AMBARI-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208236#comment-14208236
]
John Speidel commented on AMBARI-6275:
--------------------------------------
[~u39kun] thanks for your questions.
1. Yes, it will be possible to add hosts to any cluster regardless of how it
was created.
2. The initial implementation will not provide any additional consistency
guarantees. If a failure occurs, the user will need to figure out the state of
the requests tasks and then take manual steps to resolve the request. This is
a very valid request but is complicated. We will need to take some time to
define what guarantees we want to provide for REST operations.
3. Currently blueprint related meta-info is not persisted and this patch will
not add this functionality. This is also a very valid request and something
that others have asked for. We will need to look at what bp related meta-info
should be saved and how it is exposed via the api.
> 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)
