[
https://issues.apache.org/jira/browse/BIGTOP-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334388#comment-14334388
]
jay vyas commented on BIGTOP-1702:
----------------------------------
The idea is simply :
- Vagrant already is being used to install and test bigtop on VMs from scratch.
So lets
- take those exact recipes, and
- use them for installation of bigtop on manually managed machines.
That way, we don't have to curate wiki instructions on how to setup bigtop on
an n node clsuter anymore - we already have a heavily tested methodology that
we can easily validate on our laptops
> Enable SSH Provisioning for existing Cloud instance (One click BigTop
> provisioning).
> -------------------------------------------------------------------------------------
>
> Key: BIGTOP-1702
> URL: https://issues.apache.org/jira/browse/BIGTOP-1702
> Project: Bigtop
> Issue Type: Bug
> Components: deployment
> Affects Versions: 0.8.0
> Reporter: jay vyas
>
> Okay folks, I just saw https://github.com/tknerr/vagrant-managed-servers.
> Currently, we are doing a lot of maintenance of wiki pages like this:
> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+install+BigTop+0.7.0+hadoop+on+CentOS+with+puppet
> Well, why don't we just deploy w/ vagrant ? Then anyone can spin up a
> vagrant cluster using our existing VM deployers.
> I can look into it and see if it works.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
