On 09/16/2009 01:27 PM, Paul Company wrote:
Just rsync the install tree, kernels, and initrds.
We use "cobbler distro add" and then set the tree variable to point to
the "install tree"
so we don't have to have it on the local HDD.
We don't have enough HDD space on each cobbler server to hold all of
the "install trees" that we want to support.
We do have enough HDD space for the kernels and the initrds.
That's what I meant when I said "if you use cobbler distro add".
I was implying that the install tree was not local, but pointed to by
the tree variable.
Sorry if that wasn't clear.
Paul
Yes... I understand. If you want to replicate in that configuration,
before you actually run replicate you need
to make sure that the paths of all the kernel/initrds are accessible on
the target (slave) system as they are found
on the master. With those conditions met, replicate and ask replicate
to not transfer the data.
Replicate (and Cobbler) doesn't need the kernel/initrd local ... but it
does need those files to make them available for PXE (TFTP runs chroot,
among other things).
So running a script to copy over your kernels into the same place they
are on the master server (/opt/mykernels) or wherever ... and then
running cobbler replicate... is the way to go.
If on the master server the kernels are just intermixed with the trees,
you need to copy them /out/ of the trees, or just do the neccessary
mkdir -p's and scp's to transfer over just those paths. It may be
easier to just stow them in /opt or /srv or wherever on each server and
"cobbler distro edit" to change the --kernel and --initrd path.
Anyway, as long as they are in the same place on both servers before
replicate runs the equivalent edit commands for you to transfer the info
(not the data) over, life is good.
--Michael
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
