Hi,
what I do in this case is create a fact that returns which statlog are
configured. then I do the difference (stdlib) between this and what should
the machine have. Would be something like this (caution, not tested :)):
$shouldhave=['bar','foo']
$currentlyhave=$::some_fact_with_an_array_of_what_the_machine_have
$shouldnothave=difference($currentlyhave,$shouldhave)
statlog {$shouldhave:}
statlog {$shouldnothave:
purge => true #o whatever
}
regards,
On Mon, Sep 22, 2014 at 9:04 PM, Vladimir Brik <
vladimir.b...@icecube.wisc.edu> wrote:
> Hello,
>
> I have a question about automatically cleaning configuration if the
> class/define that generated it is no longer used.
>
> For example, I have a number of logging daemons that I would like to be
> able to disable automatically if their definitions are removed from the
> node's manifest:
>
> node foo {
> # "bar" and "baz" are actually names of pre-define logging
> # configurations statlog knows what to do with
> statlog { "bar":}
> statlog { "baz":}
> }
>
> This, basically, creates, starts, and enables (on boot) two new services
> "statlog.bar" and "statlog.baz". So far so good.
>
> Now, because statlog can be resource-intensive, suppose I would like the
> statlog.baz service to be stopped and disabled automatically if I remove
> statlog { "baz":} from the manifest:
>
> site.pp:
> node foo {
> statlog { "bar":}
> }
>
> Since there are many possible "statlogs", I don't want to make site.pp
> messy by explicitly doing something like the following for every one.
> site.pp:
> node foo {
> statlog { "bar":}
> statlog { "baz": purge => true}
> }
>
> Here's roughly what I am thinking of doing (but I am wondering if there is
> a better way).
>
> site.pp:
> # this is in global area of site.pp. so that all nodes, whether
> they
> # use statlog or not include this code
> class { "statlog::autocleanup":}
>
> node foo {
> statlog { "bar":}
> }
>
> statlog module:
> class statlog::autocleanup()
> {
> # real implementation is a bit more complicated to handle
> # resource ordering, non-existent services, etc.
> if !defined(Service["statlog.baz"]) {
> service{ "statlog.baz":
> ensure => stopped,
> enable => false,
> }
> }
> if !defined(Service["statlog.foo"]) {
> ...
> }
> }
>
> Is there a better way to do this?
>
>
>
> Thanks very much,
>
> Vlad
>
> --
> 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 view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/542072D9.6050500%40icecube.wisc.edu.
> For more options, visit https://groups.google.com/d/optout.
>
--
José Luis Ledesma
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAF_B3dfC_FosTcrBP1Mu5z-tpg-794hBMHu8VcVR_CxHHFcD3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
