Maciej Skrzetuski
2010-Nov-10 12:32 UTC
[Puppet Users] Managing components in an high availability environment?
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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Daniel Pittman
2010-Nov-10 23:42 UTC
Re: [Puppet Users] Managing components in an high availability environment?
Maciej Skrzetuski <m.skrzetuski@gmail.com> writes:> 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.I wrote a custom fact to determine which node in our HA database pair was currently active, and used: if $database_blah_blah == ''active'' { # manage the stuff here } For most of the resources, though, I worked fairly hard to make sure that all the administrative changes could apply on *both* nodes, so that I didn''t have to introduce that sort of dependency. This is, in my experience, the far better (but harder) way to achieve the results. Writing custom facts is actually pretty trivial, FWIW, so doesn''t add too much overhead to the whole process. (At least, nothing notable compared to the effort of getting an HA system in the first place. ;) Regards, Daniel -- ✣ Daniel Pittman ✉ daniel@rimspace.net ☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.