On Fri, Sep 12, 2008 at 05:28:16PM -0400, Michael DeHaan wrote:
Axel Thimm wrote:
> Hi,
>
> On Mon, Aug 25, 2008 at 03:20:04PM -0400, Michael DeHaan wrote:
>
>> When pxe_just_once is enabled, Cobbler is smart enough to remove the
>> per-mac-address PXE config file of a system once it is installed to
>> prevent infinite PXE boot loops.
>>
>> Currently Cobbler does this by removing the TFTP config file for that
>> particular MAC address, falling back to whatever is the default. But
>> what happens if your default system is configured, as in something like
>> this:
>>
>> cobbler system add --name=default --profile=default-profile OR
>> cobbler system add --name=192.168.0.0./24
>> --profile=default-profile-for-network
>>
>> You'd reinstall that system.
>>
>> It's been suggested that a better behavior for this is to change the
>> template the system uses and save it instead as a PXE config that
>> explicitly local boots the system.
>>
>> I can't see this breaks anyone but I figured it would be important
>> enough to mention here. (If it does, let me know, and we can talk
>> about making a config option, otherwise I'm not going to worry about it).
>>
>
> Will it be possible to have the memtest/rescue etc. profiles still
> available in that template?
If you disable netboot via the above means it will local boot, so no.
If you wanted to boot those you would instead do:
cobbler system edit --name=foo --profile=name_of_rescue_profile
or
cobbler system edit --name=foo --image=name_of_memtest_image
which would tell those systems, yes, you should PXE boot something, but
PXE boot this instead of an installation image.
Hopefully that answers the question and satisifies your use case?
The old setup would allow local admins to do some fast diagnosis w/o
having to change cobbler parameters. It would be nice if this could
still be the case by maybe reusing the same template as before but
defaulting to localboot.
Thanks!
--
Axel.Thimm at
ATrpms.net