Hello Puppet Users,

we would like to create and/or modify resources in our environment
with the help of puppet. The problem is that the software components
may fail over from node A to node B. We are planning to write our own
modules for puppet but we have no idea how to handle the fail over
thing. Is there a popular pattern for s.th. like this? S.th. like: if
the component is not on node A then look on node B and then if this
fails report a failure.

Kind regards
Maciej

-- 
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.

Reply via email to