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

David Alves commented on WHIRR-214:
-----------------------------------

Some questions:
Cluster expansion/contraction is supposed to be in a new command right (e.g. 
ModifyClusterCommand)?
As I see it it could be something like:
whirr modify-cluster --instance-templates "20 dn+tt"
(where instance-templates was before 10 dn+tt)

My question is:
What are the "old" instance templates from which we are calculating the 
difference? is it the current cluster instance templates or the configured 
instance templates?

Is there a way to rebuild instance templates based on the current cluster 
states (instead of configuration). From what I gather in ListClusterCommand the 
only thing that is retrieved is current node metadata directly from jclouds 
(node ids, addresses, etc, not the actual services running on the nodes).




> Add nodes to running clusters
> -----------------------------
>
>                 Key: WHIRR-214
>                 URL: https://issues.apache.org/jira/browse/WHIRR-214
>             Project: Whirr
>          Issue Type: New Feature
>            Reporter: Elliott Clark
>
> I would like to be able to add a node to a running cluster.
> For example if I have created a hadoop, hbase, zookeeper cluster I would like 
> to be able to add region servers to hbase,  Zookeeper nodes to the quorum,  
> and task nodes to hadoop.
> Something akin to the functionality of the hbase-ec2 script.  Where if I 
> launch a node on an already running cluster.  It is configured to join the 
> cluster.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to