I took an hour this morning to document how I use Vagrant and Puppet together to provision development VMs as well as more production-like systems. This may be entirely elementary to folks who are more fluent with Puppet, but this is an example I thought was lacking. https://github.com/blalor/vagrant-puppet-example I welcome feedback and criticism of this setup. I''m looking to minimize the difference between local development environments and production systems as much as possible. Thanks, Brian -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
I have done something similar, installing puppet master, puppetdb and a few nodes for testing, everything via vagrant. https://github.com/fsalum/vagrant-puppet Felipe On Tuesday, January 29, 2013 6:42:42 AM UTC-8, blalor wrote:> > I took an hour this morning to document how I use Vagrant and Puppet > together to provision development VMs as well as more production-like > systems. This may be entirely elementary to folks who are more fluent with > Puppet, but this is an example I thought was lacking. > > https://github.com/blalor/vagrant-puppet-example > > I welcome feedback and criticism of this setup. I''m looking to minimize > the difference between local development environments and production > systems as much as possible. > > Thanks, > Brian-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Keith Burdis
2013-Jan-30 08:48 UTC
Re: [Puppet Users] Re: Reusable Puppet config for Vagrant
Thank you both for sharing details of your Vagrant setups. This will certainly save me some time. - Keith On 30 Jan 2013 07:01, "Felipe Salum" <fsalum@gmail.com> wrote:> I have done something similar, installing puppet master, puppetdb and a > few nodes for testing, everything via vagrant. > > https://github.com/fsalum/vagrant-puppet > > Felipe > > > On Tuesday, January 29, 2013 6:42:42 AM UTC-8, blalor wrote: >> >> I took an hour this morning to document how I use Vagrant and Puppet >> together to provision development VMs as well as more production-like >> systems. This may be entirely elementary to folks who are more fluent with >> Puppet, but this is an example I thought was lacking. >> >> https://github.com/blalor/**vagrant-puppet-example<https://github.com/blalor/vagrant-puppet-example> >> >> I welcome feedback and criticism of this setup. I''m looking to minimize >> the difference between local development environments and production >> systems as much as possible. >> >> Thanks, >> Brian > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.