Also of note, if you're using Puppet 2.6.x then the command `ralsh` from 0.25.x has been superseded by the `puppet resource` command.
-Hunter On Fri, Oct 1, 2010 at 08:34, Matt Wallace <li...@truthisfreedom.org.uk> wrote: > On Friday 01 Oct 2010 15:01:25 Kikanny wrote: >> Thank you all for taking your time to explain it to me. I guess I'll >> give it a whirl and see how it goes. Another question I have is what >> if the person managing a web server does not have full knowledge of >> whatever is installed in a server or there was some other >> configuration management in place. How would I bring that under >> puppet's control? I'm asking this because we do have servers like >> that. Thanks! > > 1) Get a list of running services/open ports > 2) Get all the relevant configuration files for those services/ports > 3) Get a list of all the cronjobs on that system and the commands that are run > 4) Get a copy of all the scripts that are run by Cron > 5) Create your puppet manifests using the crontab entries, scripts and config > files as a reference > 6) Put all your puppet manifests into git/svn/mercurial/etc. > 7) Create a staging platform to test your manifests (just because puppet > parses them correctly doesn't mean that they work!) > 8) Test your manifests > 9) Test your manifests > 10) Test your manifests > ..... > 102) Test Your manifests > 103) Checkout your manifests to your puppet master (provided they have passed > the tests!) > 104) run puppet on a single server and check that your manifests give the > required results > 105) Compare the server with one that is already working (but was not built by > puppet) and try to discover why your puppet manifests aren't working in > production when they worked in staging > 106) Fix the issues > 107) Run puppet again and check that everything now works > 108) Lock down access to all your servers so the only way a change can be made > is via GIT/SVN/Mercurial etc > 109) Force commit messages for any changes to the config files > 110) Use a web interface to git to track any changes > 111) Go down the pub and by your entire team a beer for helping you achieve > the impossible. > > If it's of any help, after approx nine months, I'm at various stages of this > process between 1 and 110 for the different services that we have here... > we've > still not made it down the pub yet... :( > > Cheers, > > M. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
