Re: Site specific settings
On Wed, Jan 20, 2010 at 11:37:34AM -0500, Glenn Bailey wrote:
> On Mon, Jan 18, 2010 at 11:24:18AM -0500, Glenn Bailey wrote:
> > What's the best method to define site specific settings? I basically
> > have multiple Cobbler servers setup at various physical locations
> > and each of these locations have different DNS, NTP, Timezones, etc.
> > For DNS it appears I could use the "name_servers" option in the
> > settings file, but that would be the only one.
>
> Also cobbler-slaves in several locations here.
> The different settings (i.e. what ldap-servers are to be used for
> user-auth on the newly deployed server) are currently handed over
> by the deploying admin using ksmeta-vars.
So for each distro profile you create another distro locally that's a
slave for each distro? Seems a little cumbersome .. :-( I'm trying to
keep each distro location agnostic. It seems I would also have to make
a new name for each profile in each location as not to have them over
written when a sync happens, is this the case?
Over here we do not use cobblers sync-features. Instead all distros
directories are offered to the cobbler-slaves via rsync and can selec-
tively be fetched. Then the directory is manually made known to the
cobbler-slave as distro/profile/repo in pasting some cobbler-commands
out of a wiki into the slaves terminal. One could then also in these
commands source a text-file on that slave that contains some slave-
specific ksmetas. Should also work that everything including the
profiles gets synced to the slaves and just then a local-only profile
is copied from the provided one, additionally setting ksmeta from the
textfile.
Goes back to my original question, is there another method to do it
without creating separate slave profiles? I haven't seen any examples
for cheetah_macro's or even if this would be a good place.
Or ksmeta to be fetched dynamically from the harddisc.. maybe hooks
can help you.
Christian