1:46 a.m.
My approach is to create bootcds for a network environment where pxe is not
allowed due to an existing altiris deployment conflicting here.
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.
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'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?
4:37 a.m.
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
5:35 a.m.
On 02/26/2011 11:37 AM, Christian Horn wrote:
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
Hi Christian, So i need to enforce blank --profiles? I'll try your sed trick
regarding menu selection. Do you think this could be hacked into cobbler? I am
little bit into python and would like to see this implemented.
Regarding the old laptop issue: Is it possible to let the images/install.img
load from local (like the full install media does) and do only the installpart
over network?
Thanks!
6:10 a.m.
On Sat, Feb 26, 2011 at 12:35:38PM +0100, Gunnar Thielebein wrote:
So i need to enforce blank --profiles? I'll try your sed trick
regarding menu selection. Do you think this could be hacked into cobbler? I am
little bit into python and would like to see this implemented.
Could probably get implemented.
My first attempt was manually editing /etc/cobbler/pxe/*, didnt help.
Also for PXE disabling the menu is implemented, i.e. via setting in
the settings-file.
Did also sumble upon other things when using buildiso: when deploying
suse sles it didnt hand over kernel option autoyast= but still ks= as
for rhel, while the PXE-files are correctly deployed. So its probably
just few/no people havent had your requirement yet.
Regarding the old laptop issue: Is it possible to let the
images/install.img
load from local (like the full install media does) and do only the installpart
over network?
Not sure about that. There are in general vmlinuz/initrd and all the later
repo-data which can be supplied using different methods. Have only seen
install.img beeing supplied from the same location as the repo-data.
Starting with Fed15 the install.img seems to be part of the initrd.
Christian
4833
days inactive
4833
days old
cobbler@lists.fedorahosted.org
3 comments
2 participants
participants (2)
-
Christian Horn -
Gunnar Thielebein