Cobbler's starting to share just a few functions with koan.
Dual maintaince seems to be a /bad/ thing to me, so any objections to cobbler requiring koan? Creating a cobbler-common package is something I very much want to avoid.
Koan does /not/ require libvirt, so what it pulls in is minimal.
--Michael
Am 08.01.2009 um 21:30 schrieb Michael DeHaan:
Cobbler's starting to share just a few functions with koan.
Dual maintaince seems to be a /bad/ thing to me, so any objections to cobbler requiring koan? Creating a cobbler-common package is something I very much want to avoid.
Koan does /not/ require libvirt, so what it pulls in is minimal.
If both still build under RHEL5, I don't see a problem (I never tried koan).
Rainer
Rainer Duffner wrote:
Am 08.01.2009 um 21:30 schrieb Michael DeHaan:
Cobbler's starting to share just a few functions with koan.
Dual maintaince seems to be a /bad/ thing to me, so any objections to cobbler requiring koan? Creating a cobbler-common package is something I very much want to avoid.
Koan does /not/ require libvirt, so what it pulls in is minimal.
If both still build under RHEL5, I don't see a problem (I never tried koan).
Rainer _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Correct, it does.
koan serves two functions:
(A) enabling virt installations from cobbler profiles (B) enabling system replacement without PXE, for networks that can't netboot and have some working machines they want to reinstall/update in an automated way.
cobbler@lists.fedorahosted.org
-
Michael DeHaan -
Rainer Duffner