[
https://issues.apache.org/jira/browse/BIGTOP-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771979#comment-13771979
]
Sean Mackrory commented on BIGTOP-1072:
---------------------------------------
Just throwing in a general vote of support for efforts like this.
{quote}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. {quote}
There was a discussion a while ago on what we might replace Boxgrinder with
since it is no longer supported by Red Hat and is already, IMO, showing it's
age. I've been using Packer.io for some of my work and I quite like it. I've
been thinking about proposing some code to build a Bigtop appliance with
Packer, in fact. If we do go this direction, it's worth pointing out that
Packer and Vagrant come from the same guy - and you can easily produce Vagrant
boxes with Packer.
Also, Vagrant allows provisioning with puppet - for which we have a lot of
deployment code! Probably not something you'd want to run everytime you spin up
an instance of the box, but just a suggestion for how this work could 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
