Thanks for the replies, and indeed we are working with cobbler. It helps that the first application will be kickstarting RHEL-derived systems, as that's right in line with cobblers core competency.
I'm less confident (and therefore more interested in hearing your experiences) about how we're going to pull in legacy systems and drive, say, dns zonefile generation for VIPs, Cnames, and other resources we need to know about but which don't make a lot of sense to manage inside cobbler itself. Do you just put that kind of thing as static entries in the templates? Just add them as hosts? Or extend cobbler in some way to deal with external resources? Thanks again to all who responded, this helped shut down some avenues of investigation which would have soaked up a lot of time. -=Eric On Jul 7, 2010, at 3:59 PM, Matthew Barr <[email protected]> wrote: > > On Jul 7, 2010, at 5:59 PM, Eric Sorenson wrote: > >> I'm at the point (again) where I am automating and taming a large site. I >> take it as a tenet of faith that the foundational underpinnings of the >> infrastructure ought to be driven by a database with well-defined APIs for >> getting info in and out of it - so an operator can put in a new host's >> serial number and MAC address, pick a role that the system ought to be >> configured as, and kick off IP allocation, DNS, DHCP, configuration >> management and monitoring. I have seen the promised land, it worked really >> really well, but our team wasn't allowed to release it. > > The thing that might do most of what you want is Cobbler, from RedHat. It > doesn't do the full CMDB database, but it comes pretty close, and I've used > it to do most of the things you talk about. > > > I can write up more of how we used to integrate it w/ CFengine, but in short, > cobbler brings the machine up and provides DHCP & build infra, to bootstrap > CFengine. From there, you can do whatever you need to, in terms of > configuration & packages, etc. We used a DB to store roles, classes, etc. > > https://fedorahosted.org/cobbler/ > > > 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/
