> 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 On Wed, Sep 16, 2009 at 9:34 AM, Michael DeHaan<[email protected]> wrote: > On 09/16/2009 11:53 AM, Paul Company wrote: > > If you are blindly copying over the cobbler definitions, you might as well > /not/ use replicate because you're doing it all yourself. > > > Bottom line: > "cobbler replicate" in version 1.6.6 doesn't work when you use > "cobbler add distro." > It only works if you use "cobbler import." > > > Not saying that -- You are responsible for moving your data if you haven't > used import. > > There is no wrapper that I can see that makes it work without > incurring some kind of risk. > > > Just rsync the install tree, kernels, and initrds. > > Do not rsync the config.d. > > I either have to wait for 2.2 (according to Scott) or I have to write > my own replication script. > > > Should I file a bug report for this issue? > > > > No, I think you are fundamentally understanding what it does and does not > do. It is all rather simple. > > All you need to do is transfer your data (or make it available in the same > storage paths) before running the replicate command. > > > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
