[
https://issues.apache.org/jira/browse/BIGTOP-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863303#comment-13863303
]
Evans Ye edited comment on BIGTOP-1171 at 1/6/14 7:33 PM:
----------------------------------------------------------
Hi Jay, good news!
I've work out the first version of the patch. Please allow me to have a brief
introduce to it:
1) In this patch, hadoop and hbase will be deployed on a centos 6 VM using
vagrant's puppet provisioner and bigtop's puppet recipes.
2) The puppet recipes located on host machine will be configured to be a shared
folder in guest VM to retrieve the configuration file.
3) You can add or remove components easily through configuration file which is
located at {{bigtop-deploy/puppet/config/site.csv}} on the host machine.
4) The base VM box is provided by
[puppetlabs|http://puppet-vagrant-boxes.puppetlabs.com].
One thing to let you know is that I was trying to work out the patch based on
fedora19 box (same one with BIGTOP-1072),
but the official puppetlabs' repo only provides puppet 3.x for that OS version.
To let our puppet recipes support puppet 3, we need to get BIGTOP-1047 patched,
but there should be a backward compatibility issue exist.
Another thing is that I found there's a bug on the current puppet recipes:
BIGTOP-1174, so if you would like to try the patch out, you may need to execute
the puppet provisioner again({{vagrant provision --provision-with puppet}})
after {{vagrant up}}.
was (Author: evans_ye):
Hi Jay, good news!
I've work out the first version of the patch. Please allow me to have a brief
introduce to it:
1) In this patch, hadoop and hbase will be deployed on a centos 6 VM using
vagrant's puppet provisioner and bigtop's puppet recipes.
2) The puppet recipes located on host machine will be configured to be a shared
folder in guest VM to retrieve the configuration file.
3) You can add or remove components easily through configuration file which is
located at {{bigtop-deploy/puppet/config/site.csv}} on the host machine.
4) The base VM box is provided by
[puppetlabs|http://puppet-vagrant-boxes.puppetlabs.com].
One thing to let you know is that I was trying to work out the patch based on
fedora19 box (same one with BIGTOP-1072),
but the official puppetlabs' repo only provides puppet 3.x for that OS version.
To let our puppet recipes support puppet 3, we need to get BIGTOP-1047 patched,
but there should be a backward compatibility issue exist.
Another thing is that I found there's a bug on the current puppet recipes:
BIGTOP-1174, so if you would like to try the patch out, you may need to execute
the puppet provisioner again(vagrant provision --provision-with puppet) after
{{vagrant up}}.
> Puppetize the Vagrant deployer
> ------------------------------
>
> Key: BIGTOP-1171
> URL: https://issues.apache.org/jira/browse/BIGTOP-1171
> Project: Bigtop
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Labels: patch
> Attachments: BIGTOP-1171.1.patch
>
>
> The next iteration of the 1072 (vagrant recipe for deployment) would benefit
> alot from directly provisioning via puppet, rather than hardcoding the shell
> commands.
> HOW THE CURRENT PROVISiONER WORKS:
> The shell provisioner manually wget's the repos and installs components using
> yum.
> HOW THE PUPPET BASED PROVISIONER WILL WORK:
> In this JIRA, the aim will be to write a new provisioner that is puppet
> based, which simply manages a site.csv file for a default vagrant deployment.
> Then, the end users can update the site.csv, run "vagrant up", and have a
> puppet based distro up and running. The biggest advantage will be that the
> the vagrant deployer will continually be updated by the evolution of the
> puppet repos, rather than needing manual updates.
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
