ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes Klein (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-6275) Add support for "add hosts" with Blueprints API
Date Tue, 16 Dec 2014 19:23:13 GMT

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

Johannes Klein commented on AMBARI-6275:
----------------------------------------

Being able to specify size of host group instead of having to list host names would improve
cloud deployments significantly. Host agents could check-in with Ambari server and register
with host group. Ambari could filter by host properties or host agent could be pre-configured
with host group token. 

In case of hosts configured for master components such a RM, Name Node etc. configuration
would have to refer to host group instances generically. Ambari would have to update configuration
and propagate configuration to slave nodes to trigger registration, i.e. to allow data nodes
to register with name node etc.  

> Add support for "add hosts" with Blueprints API
> -----------------------------------------------
>
>                 Key: AMBARI-6275
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6275
>             Project: Ambari
>          Issue Type: Epic
>          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)

Mime
View raw message