This message was deleted.
# harvester
a
This message was deleted.
c
harvester can use pxe boot for sure, can you provide more specific detail about your environment?
h
sure, I have the node installing from pxe just fine. my problem is that after install the node will reboot (as is normal) and then pxe boot to the installer again (and again)
šŸ¤” 1
my env is a openstack-ironic deploy, it's expecting to either always pxe boot or to pxe boot once and lay down an image to disk (raw disk image or qcow2)
having harvester pxe boot to it's own installer is kinda out of scope
I think the two products / tech just do not work well together šŸ˜ž I'd like to use ironic to manage nodes DC wide if I can
c
can you check this node's boot order? maybe network card has overrided hard drive?
h
network card does take priority, I was trying to get the node booted without manual intervention (selecting pxe boot from bios)
c
the boot order should change once the installation finished, which version are you installing?
I'm not very familiar with openstack though, when using seeder, which is a tool that automatically manages and provisions harvester cluster on baremetal machines, it will serve PXE boot only once, after harvester installed the nic will not boot up since the PXE server stopped serving them
Maybe you can check out how openstack-ironic manages PXE serveršŸ¤” they should not boot up with nic again if you finished installation
h
there are two ways that openstack ironic boots servers. One is direct, where it will boot the 'ironic python agent (installer) and write a disk image to disk, it'll do this just once then boot from disk. I don't think this fit's harvesters model til that pull request I linked is available (provides disk images). The other is ramdisk, this method always boots the pxe image, this half fits harvesters model. but since it's always boots the pxe image it'll constantly reinstall.
šŸ‘€ 1
r
Just came across this thread ā€¦ If I recall correctly, Ironic will use something like
ipmitool chassis bootdev pxe
to set the one-time boot device for the target machine. The boot order in BIOS is better to keep the ā€œhard driveā€ above ā€œnicā€ so that after the installation is completed, the machine can boot from the disk without intervention. Regarding the first way for ironic to boot servers, Harvester installation will have an ā€œinstall modeā€ in the upcoming release. It basically streams the image and writes it to the disk. Seems a perfect fit.
h
ya, I'm watching that pull request, can't wait to have a qcow2 file to install instead
šŸ‘ 1