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

Konstantin Boudnik commented on BIGTOP-1178:
--------------------------------------------

I think I should resort to someone's else expertise in Vagrant, which would be 
more extensive than mine - likely [~bmahe]. While I can read this code and it 
looks ok to me, I won't be possible to spot issues just by reading this. Hence, 
can't really make an official review.

> Clusterize the puppetized vagrant deployer.
> -------------------------------------------
>
>                 Key: BIGTOP-1178
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1178
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Deployment
>    Affects Versions: 0.7.0
>            Reporter: jay vyas
>            Assignee: jay vyas
>            Priority: Minor
>             Fix For: 0.8.0
>
>         Attachments: BIGTOP-1178.1.patch, BIGTOP-1178.2.patch
>
>
> Now that BIGTOP-1171 is nearing completion (puppetization of vagrant), we can 
> move towards setting up a real hadoop "cluster".
> The goal here will be to allow us to do more with vagrant than just spinning 
> up a single VM.  To scale the vagrantfile, we can do something like :
> {noformat}
>  if ARGV[1] == 'cluster'
>         cluster = true
>     else
>         cluster = false
>     end
> {noformat}
> I think the Vagrantfile can look something like this: 
> {noformat}
> Vagrant.configure(VAGRANT_API_VERSION) do |config| 
>     # Head node   
>     config.vm.define :bigtop1 do |bigtop1|
>      
>    # If "cluster" then add a bunch of slaves also 
>    if cluster == true
>             # Slave nodes .... 
>             config.vm.define :bigtop2 do |bigtop2|
>             config.vm.define :bigtop3 do |bigtop3|
>             config.vm.define :bigtop4 do |bigtop4|
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to