[
https://issues.apache.org/jira/browse/BIGTOP-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108944#comment-14108944
]
Evans Ye edited comment on BIGTOP-1416 at 8/25/14 1:31 PM:
-----------------------------------------------------------
With this refactory, now we can directly use {{vagrant up}} to spin up a hadoop
cluster and use {{num_instances}} to control the node number.
I've also updated the REAME.md within the patch, so feel free to give it a try
and leave some feedback to me.
was (Author: evans_ye):
With this refactory, now we can directly use {{vagrant up}} to spin up a hadoop
cluster and use {num_instances} to control the node number.
I've also updated the REAME.md within the patch, so feel free to give it a try
and leave some feedback to me.
> Refactor vagrant-puppet's Vagrantfile to make instance number configurable
> --------------------------------------------------------------------------
>
> Key: BIGTOP-1416
> URL: https://issues.apache.org/jira/browse/BIGTOP-1416
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 0.7.0
> Reporter: Evans Ye
> Priority: Minor
> Attachments: BIGTOP-1416.1.patch
>
>
> Current version of
> [vagrant-puppet|https://github.com/apache/bigtop/tree/master/bigtop-deploy/vm/vagrant-puppet]
> only support 1(single) or 3(cluster) node deployment.
> There's a more elegant way to make the node number configurable by given a
> {{$num_instances}} variable instead of copy and paste new nodes and modify
> its name in Vagrantfile.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
