Re: minimal bootcd for pxe-less environment
On Sat, Feb 26, 2011 at 08:46:55AM +0100, Gunnar Thielebein wrote:
1. The bootcd should be connected via iLO or presented as virtual image to the
destination system (VM).
2. It should be possible to restrict the bootcd to exactly one host system.
3. The bootcd should be used from the systems without any other user intervention.
4. The bootcd should be keepen as slim as possible, installation data can be
carried per http through the net.
5. The boodcd should be creatable from the webinterface.
'cobbler buildiso <parameters>' sounds good for these requirements - apart
of
the last one, cant comment on that.
How could that be done via cobbler?
I've made tests with cobblers buildiso feature. What i've found out it is not
possible to restrict systems to one hosts. Either the profiles are shown in the
selectable also the option to boot from local harddrive is preselected. Is this
configureable somewhere?
I didnt see buildiso as configurable directly, but you can use a workflow like
this, wrapped in a small shellscript that not to hard for daily use:
# generate iso with default to local
cobbler buildiso --profiles='' --systems=sakura
# modify defaulting to your host
sed -ie 's,^DEFAULT.*,DEFAULT sakura,' /buildiso/isolinux/isolinux.cfg
# generate custom iso using the mkiso-commang also buildiso was using
mkisofs -o /root/generated.iso -r -b isolinux/isolinux.bin -c isolinux/boot.cat \
-no-emul-boot -boot-load-size 4 -boot-info-table -V Cobbler\ Install -R \
-J -T /buildiso
I've made tests with an old 256MB laptop. What I wonder is that
PXE images works
flawless and also the installation from image through "buildiso --standalone".
But when using a slim bootcd as an source I always get the message "Your system
has not enough memory to use this kind of installation!"
Where is the big difference here?
Tried older Fedoras/Centos/RHEL for fun?
The requirements increased over time.
Christian