On Mar 26, 2009, at 2:52 PM, timcharper 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.
This should be very straightforward, and I do it constantly.
Of course, if you're just testing, you can almost assuredly get
exactly the same behaviour by just running 'puppet' against your
site.pp and pointing it at your conf file - there's usually no need
for the client/server.
--
Morgan's Second Law:
To a first approximation all appointments are canceled.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
