In regard to: [Puppet Users] Need advice how to architect solution for...:
I'm having difficulty determining the best course of action how to implement /etc/resolv.conf on my RHEL5 hosts. Here's my requirements, IN ORDER OF PRECEDENCE: * All hosts, regardless of function, need /etc/resolv.conf * Dependiing upon which environment the host lives in (i.e. Facture $domain) this changes search paths and nameservers to use in /etc/resolv.conf * Any host defined as a 'DNS Server' should ignore environment specific settings and use nameserver of '127.0.0.1' * There are one or two one-off DNS servers that should have their own per-host settings which shall override all previous definitions.
We're doing something like this, although I need to expand it to be a little bit smarter, but wouldn't setting something like --- named_type: client # or 'caching', 'secondary', 'primary' in your extdata/hiera/ENC and then using a selector in your class to pick which template to use for resolv.conf essentially solve all of this?
The only things that need to change between these rules are the values of the search path and the list of nameservers. So I would like to use a single template for /etc/resolv.conf which simply plug in data available in variables accessible by the template
You probably could do that, but I think the template will be more complicated this way. Selecting different templates based on what type of system it is makes the template simpler. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
