Yes, I recognize that would be a solution, and likely a good one, however I believe in order for us to be able to test puppet changes before committing and pushing them to the server, we'd all have to boot our own series of VM's (in other words, we don't have a single sysadmin). Tim
On Thu, Mar 26, 2009 at 2:30 PM, Brian Mathis <brian.mat...@gmail.com>wrote: > > That's what VMware is for. > > > On Thu, Mar 26, 2009 at 3:52 PM, timcharper <timchar...@gmail.com> wrote: > > > > I'm wanting to build something along the lines of: > > > > * I close the puppetmaster repo locally > > * I start it up, puppetmasterd --confdir ~/path/to/conf > > * I ssh in to the machine I want to work with, using ssh -R > > 8140:127.0.0.1:8140 > > * Then, on the remote machine, I run puppetd --test --server 127.0.0.1 > > > > Is this crazy? Is there a better way, more established way to do > > something like this? > > > > My main interest is to be able to have a testing puppetmaster that I > > can update and hit while working on a specific instance, get it > > working, and then merge it to our main puppet master. Currently our > > staging environment is being run on the same boxes as production, so > > we don't have the luxury of a separate cluster. > > > > Thanks :) > > > > Tim > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
