Set the IPMI power type to boot from a custom boot option rather than PXE

Users
,
3

Hey @r00ta

Thanks, yeah that helps a lot.

Let me expand a bit on the situation and try to be more concise, perhaps I missed a few details:

  1. I am running in an environment that cannot use PXE / DHCP.
  2. I am trying to work around that so I can still use maas, and I am following the advice given on this similar thread.
  3. based on that, I took the my maas’s ipxe script from /var/lib/maas/boot-resources/current/ipxe.cfg, that has this content:
#!ipxe
# MAAS iPXE pre-loader configuration file

# Load based on MAC address first.
chain http://${next-server}:5248/ipxe.cfg-${mac} ||

# Failed to load based on MAC address.
chain http://${next-server}:5248/ipxe.cfg-default-amd64

and built an ISO image with iPXE with the following command (maas.ipxe is the ipxe script that I included): make bin-x86_64-efi/ipxe.efi EMBED=maas.ipxe, based on the instructions here, and according to the advice on the maas thread.

  1. I mount this ISO on my server, and tell maas to commission it, it loads the iPXE script and commissions perfectly.
  2. I deploy using the same method, this works perfectly as well, now Ubuntu is installed.
  3. The problem starts here. When I try to redeploy, maas seems to tell the server to try and boot via PXE, but PXE isn’t supported, so it will just end up booting to Ubuntu normally.
  4. My idea was to create a new BIOS entry that will point to the iPXE script as a boot option, and when maas needs PXE, it will use that instead of PXE, which should work (tested and verified manually that it works), but I do not know how to get maas to tell the server to use this boot method instead of PXE.

Hope that makes things clearer.

Thanks!