You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Evans Ye (JIRA)" <ji...@apache.org> on 2014/03/06 11:44:42 UTC

[jira] [Updated] (BIGTOP-1178) Clusterize the puppetized vagrant deployer.

     [ https://issues.apache.org/jira/browse/BIGTOP-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evans Ye updated BIGTOP-1178:
-----------------------------

    Attachment: BIGTOP-1178.2.patch

> Clusterize the puppetized vagrant deployer.
> -------------------------------------------
>
>                 Key: BIGTOP-1178
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1178
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Deployment
>            Reporter: jay vyas
>            Priority: Minor
>         Attachments: BIGTOP-1178.1.patch, BIGTOP-1178.2.patch
>
>
> Now that https://issues.apache.org/jira/browse/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)