Geoff Crompton schrieb: > Currently, if I want to remove resources from a node that I've > previously configured, I'm doing 'anti' patterns. Is there away for > puppet to do it for me? For example, if I started with:
[...] > If that is possible (or could be built in), could you make puppet > automatically remove that resource from the client system if it detects > a resource has been removed? I've using two recipes to solve such problems: The first is extensive use of purging. For example, I put apache's virtual host definitions into a directory that is set to purge, with one file per virtual host. So if I stop managing a virtual host, puppet will automatically remove the file containing the configuration and notify (via the directory) apache to reload. The other recipe doesn't use puppet directly, but is only enabled by it: One Server Per Node. Lightweight containers like Linux-VServer, OpenVZ, BSD's jail or Solaris' zones allow us technically to have a separate OS instance for every service we run. Puppet allows us to manage them too. Once you have this in place, you can just destroy the container if you no longer need the service, or re-image its contents when there are fundamental changes. Regards, DavidS -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
