On Feb 12, 2013, at 5:35 AM, Ralph Bolton <ra...@coofercat.com> wrote:
> Thanks for the suggestion. I did wonder about copying all the modules and > configs off the Puppet Master onto the test box. My concern is really just > about keeping that lot up to date, and most importantly to make sure that it > behaves the same as it would do if it came from the Master. It could be done > this way, but I'm worried it seems simple now, but will turn into a headache > later on. If this is the only way to do it, then I guess I'll just have to > suck it up :-( You may find this helpful: https://github.com/blalor/vagrant-puppet-example It's an example project I put together a couple of weeks ago to model how you can share the same puppet config across multiple environments, like production and in a Vagrant VM. There's very little difference between running "puppet apply" and an agent checking into a master (aside from the obvious missing management pieces) but the manifests and modules can (and should) be largely the same. If you've go the master config checked into version control, you should be able to use that same source locally, albeit with a local nodes.pp "shim" that emulates the classes applied by the master. I'd recommend designing your config this way from the start :-) but I've gone this route a couple of times, now (I have access to the source for manifests but no influence on the master). 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+unsubscr...@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.
