On Tue, 7 Sep 2010, Brodie, Kent wrote: > The upside of course is- centralized management of host info. The > downside is that you have now added another dependency for all of the > servers - so DHCP server robustness is absolutely critical.
True. However, it's fairly easy to do HA on DHCP, when it's a pool of static reservations. You don't have to fight over keeping track of which IP's are in use, etc- you can just have a few servers running duplicate confs, and which ever responds first, no problem. I've set it up to generate the DHCP conf via Cobbler, then sync that file out to the NAS, which is then diffed, copied, verified, and loaded onto the prod DHCP servers. We actually put DHCP, DNS, and LDAP on single boxes, and considered those our primary boot first boxes. Almost nothing would work w/o those services. Each of them has some reasonable highly available option, and made life easy. We actually didn't run the masters on those boxes- those were slaves. Masters tended to be VM's for DNS & DHCP. It was nice to shield the load from the masters, and kept things very consistant between the slave boxes. Matthew _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
