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/01/06 20:34:52 UTC

[jira] [Updated] (BIGTOP-1171) Puppetize the Vagrant deployer

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

Evans Ye updated BIGTOP-1171:
-----------------------------

    Attachment: BIGTOP-1171.1.patch

> 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)