I''m working with a customer that has a set of machines that provide services. One machine has DNS on it, another radius, and another syslog. One of the issues that comes up is that someone makes a change on the DNS machine that could potentially break the radius configuration. The process now is when the DNS change takes place, to restart the radius server and verify it still works. The syslog server has a firewall that needs to be modified when a new host is added as well. This seemed like a perfect use for something like puppet. All of these machines are dependant (maybe connected to is a better word here) on the changes that take place on the DNS server. Is it crazy for me to think that using puppet in this environment would help me solve my problem? I''m stuck on how to begin getting this done. Mike B. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Aug 22, 2007, at 11:36 AM, barsalou wrote:> > All of these machines are dependant (maybe connected to is a better > word here) on the changes that take place on the DNS server. > > Is it crazy for me to think that using puppet in this environment > would > help me solve my problem?No, I don''t think it''s crazy, but Puppet is not yet very good at dealing with multi-host interactions. There are basically two ways to configure multiple hosts at the same time: Use export/collect, which is meant for exactly that, or have a class that configures all hosts, but uses conditionals to work correctly on each: class dnsthing { if tagged(dnsserver) { ... do dns stuff ... } if tagged(radiusserver) { ... do radius stuff ... } } -- I never think of the future. It comes soon enough. --Albert Einstein --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com