On Apr 9, 2015, at 1:26 AM, Gabriel Filion <[email protected]> wrote: > > Hello, > > A client of mine needs to be able to control which hours during the day > a certain daemon is running and which hours it is not. > > So far I can think of hiera for controlling the on/off periods + some > math magic to determine in the puppet manifests whether we are currently > in the On or Off period (which would ensure either "running" or "stopped").
This seems like an overly-complex approach. > The other option could be a custom fact (which would make manifests less > complicated), but I'm unsure of how control over the on/off time periods > could be achieved in this case. > > Am I more or less on to something with the above or am I trying to do > something with the wrong tool? One of the downsides of using puppet is > that runs are only once per hour (in that case) so the starting and > stopping times might be unreliable :\ Puppet is really good at managing steady states. Why not have puppet manage cron entries responsible for starting and stopping the daemon? A custom fact could be used to return the current on/off state (accurate as of the last puppet run, or course) of the daemon for auditing purposes. -- Peter -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7DA458FE-70F8-4A5E-857F-6140FE49523E%40gmail.com. For more options, visit https://groups.google.com/d/optout.
