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?
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler

Reply via email to