Yeah. If I'm not mistaken the Cobbler pxe_just_once scheme relies upon pulling mac addrs into and out of the tftpboot files (ie netboot disabled means "I have no tftpboot boot entry for your mac addr.") This scheme breaks down if one chooses to hand out ip addrs (dhcp) and boot info (tftp) anonymously ie to *any* requesting mac. When the ipmi pxe just once option is available, it gives us a means to decouple the boot preference from the mgmt of dhcp/tftp config files.
On Wed, Aug 13, 2014 at 12:25 PM, Nishanth Aravamudan < n...@linux.vnet.ibm.com> wrote: > On 13.08.2014 [16:56:15 +0200], Andr? Gem?nd wrote: > > They act on two different levels. The ipmi chassis bootdev pxe command > > really sets the device that the BIOS probes for booting. That way you > > don't need to set your machine boot order to prefer network boots > > permanently in BIOS, but can leave the default and change it ad-hoc. > > We also use this (but trigger it manually). > > Right, to make it explicit: > > pxe_just_once is a Cobbler-level configuration bit, which tells a > Cobbler snippet to unset "netboot-enabled" for a system when it finishes > the install (that actually is in the snippet itself). So it translates > to "configure the Cobbler server to PXE boot this system once". > > The IPMI command is on the physical system (target) and tells it to use > the network interface to boot on the next boot. The boot after that > should go back to the default boot order (unknown to Cobbler). So it > translates to "configure the victim server to PXE boot on the next > reboot". > > Thanks, > Nish > > _______________________________________________ > cobbler mailing list > cobbler@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/cobbler >
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler