On Fri, Feb 19, 2010 at 4:40 PM, Dan <[email protected]> wrote: > Forgive my ignorance, but puppet and ruby are both very new to me. > > I am trying to use puppet for (amongst other things) manage a custom > backup script i use on all my machines. The script reads a > configuration file that tells it where to backup from and to. Every > machine is different, some only backup a single folder where others > backup many folders (an example config file is below). I figure the > best way to do this with puppet would be to create a template > configuration file for the backup script and add the custom > definitions in each node manifest.
The best (read: absolute dirt simplest) approach I've found is to have all nodes load a common Puppet module to: 1 create the master backup script, which slurps in every file in, say /etc/backups.d 2. creates a cron entry to run the backup script 3. setup a definition to generate a 'snippet' file in /etc/backups.d Your jboss module can just 'include backups' and use the definition to create it's own snippet directory. Like I said, it's dead simple - I'm sure there are better ways using things like exported resources and storeconfigs, but this approach is working fairly well for us to do things like apache vhosts, firewall rules, etc. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
