On 09/07/15 02:26, Gerard Kok wrote:
You could create a custom fact that returns the desired state of the
service, based on the existence of the file, and then use the value of
that fact in the service declaration. For example, like so:
The custom fact:
|
Facter.add(:state_of_the_service)do
setcode do
File.exists?(the-file)?"running":"stopped"
end
end
|
and the service declaration:
|
service {'the-service':
ensure=>$::state_of_the_service
}
|
The downside of this solution is that you'll require two puppet runs to
get the service running if the file is (indirectly) created by puppet.
The first run the file will be created, but the fact is computed at the
start of the run, so it will still be 'stopped', and only switch to
'running' at the start of the second run.
Actually that is not a problem (the setup concerned - puppet-swift -
already requires a number of runs).
I've used this approach, and it seems to work fine - awesome!
The only consideration is that this logic is actually in an external
module (puppet-swift) todo with classes that are called by the module
internally...so I'm patching the module :-( I've started a discussion
about this on the openstack-dev list to see if they like this approach
or not.
Thanks for your help
Mark
--
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/559F17CB.9060603%40catalyst.net.nz.
For more options, visit https://groups.google.com/d/optout.
