[
https://issues.apache.org/jira/browse/BIGTOP-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jay vyas updated BIGTOP-1072:
-----------------------------
Attachment: BIGTOP-1072.1.patch
Hi bigtop ! I have a special holiday surprise for you !
vagrant setup of a bigtop box :) This vagrant recipe will install and spin up
a single fedora 19 vagrant box, install bigtop YARN, and then start a mapreduce
job for you.
It uses a vagrant fedora19 box that we host publically as the basis.
Its a first iteration, but ive tested it and it works . To test it locally.
1) Install virtualbox.
2) (very easy, and optional if you want to comment out " bigtop1.cache.enable
:yum") Install the yum cachier vagrant plugin :
https://github.com/fgrehm/vagrant-cachier
3) vagrant destroy --force && vagrant up
After a few minutes, you should see "calculate pi" starting up.
I've basically stolen this recipe from the READMEs in the bigtop-deploy docs.
But if this seems useful, maybe as a next iteration i can put in a subproject
which builds a bigtop smoke testing environment, so that we can run smoke tests
in VMs while developing them, or alternatively , we could use them for things
like meetups / hackathons / etc, to make sure everyone has the same
reproducible hadoop dev environment.
Anyways, comments are welcome. If its to raw to put into bigtop main fork just
let me know and ill refine it some more, but i think its probably a pretty good
start :)
> Vagrant scripts for spinning up and "hydrating" bigtop vms
> -----------------------------------------------------------
>
> Key: BIGTOP-1072
> URL: https://issues.apache.org/jira/browse/BIGTOP-1072
> Project: Bigtop
> Issue Type: Bug
> Reporter: jay vyas
> Priority: Minor
> Attachments: BIGTOP-1072.1.patch
>
>
> Vagrant is a tool that spins up VMs for you and destroys them. The only real
> requirement it has is that a "base box" has been created before hand.
> At that point, you can install the VM using different provider hosts
> (kvm,virtualbox,etc...).
> The goal of vagrant is to unify VM environments for developers with
> production env. This is very similar to what bigtop aims at providing.
> Vagrant adds host/guest shared directories, static ips, and allthe other
> goodies that one has to configure manually, into vm provisioning in a vendor
> neutral fashion: Essentially giving a declarative API to VM creation.
> I would like to suggest that bigtop provides / maintains vagrant startup
> scripts that layer hadoop tools on top of a "base box" vm. This is slightly
> different than the current strategy which creates a full blown VM with hadoop
> on it. The vagrant approach provides a means for more developer
> customization of the vm artifacts being used without adding any real overhead
> (other than having vagrant installed and understanding the very simply
> vagrant recipe for creating a vm).
> Probably in the begining this could be complimentary to the boxgrinder
> created VMs, and over time, maybe people would migrated to using the vagrant
> provisioned VMs as they become more popular and use of vagrant gets more
> common in the community.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
