On 10/18/2010 3:13 PM, jcbollinger wrote:
On Oct 18, 5:19 am, Daniel Maher<d...@witbe.net> wrote:
I am curious to know what is the best practice for removing a module
(and the resources it maintains) from a system ?
[...]
I have occasionally written sub-modules to do the work of cleaning the
resources away (ex. « webservice::no »), but this seems ridiculous, and
is an administrative pain besides. What sorts of approaches might there
be to make this for manageable ?
I'm guessing you mean you have written sub-*classes* to do that job.
That is indeed the Puppet way to do it, and I don't find it at all
ridiculous.
Perhaps you already understand this, but you do not grok Puppet until
you know in your bones that Puppet is about achieving and maintaining
*state*, and only incidentally about doing particular work. In this
case, the state detail you achieve _and maintain_ is that the web
service is not installed. If it is important to you that the service
be absent from certain nodes, then why is it ridiculous for Puppet to
maintain that?
Exactly. If done right, this can be achieved by using purging on the
proper directories (like /etc/http/conf.d) to keep away unmanaged
contents. For the most things this obviates the need for a ::no class
altogether.
Best Regards, David
--
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 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.
