On Tue, Mar 24, 2009 at 2:28 PM, Jim Wildman <jim(a)rossberry.com> wrote:
On Tue, 24 Mar 2009, JAmes Atwill wrote:
> Hi,
>
> I'm curious how people bootstrap their initial cobbler instance. My cobbler
installation is a VM on a Xen Host which involes configuring a base system, then a VM,
then cobbler. Has anyone come up with any other clever ways of automating this?
>
> JAmes
>
We use an rpm package (cobbler-config per se), that has all the right
dependencies, snippets, users, drops in an appropriate (to our env)
/etc/httpd/conf.d/cobbler.conf, etc. yum install that guy, start the syncs
and you're off (we haven't automated the syncs because of disk space,
bandwidth/scheduling issues).
We have versions for el4 and el5 bases. The base OS may be preexistent,
or can be built from one of the existing cobbler servers.
Another trick we use is to have a "cobbler.$SITE" for in dns for every
site where $SITE is in the search path in /etc/resolv.conf. That
allows us to put "server: cobbler" in /etc/cobbler/settings and have
that file be identical for every one of our various slave sites. It
might not make sense for you if you aren't replicating to colos all
around but in our environment we need to.
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com