ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Newton Alex (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-6275) Add support for "add hosts" with Blueprints API
Date Wed, 22 Oct 2014 00:12:34 GMT

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

Newton Alex commented on AMBARI-6275:
-------------------------------------

I like John's approach. A REST end point should ideally do only one thing. So doing the post-add
tasks should not be tied to the add-hosts REST end point. It should be the UI's job to make
it easier for user. The REST APIs are targeted mostly for machines or developers.	

Some questions:
1. In case of reference node approach, what would be the response if there are master roles
and slave roles on the node. E.g. Zookeeper nodes (master) and Datanodes (slaves)?
2. Will agents have to be pre-installed on the newly added nodes?
3. Should this API be aware of cluster security? How does Ambari add security to newly added
nodes today? Are there separate APIs for doing that? 

BTW, is there a plan for removing nodes too (may be in a different ticket)?

Thanks

> 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)

Mime
View raw message