On 2025-10-22 10:30, Sean Mooney wrote:
i dont have the tftp/pxe infra setup locally to test this end to end but that image should work provided security groups or other firewalls are not blocking the dhcp request and subsequent pxe boot packets. The pxe infrastructure works just fine, the installation is successful and all, but it doesn't work unattended in that we have to select the respective boot entry. I'll need to do some more testing and all, but right now I feel like getting the xml definition of a VM to boot from network is the easiest way to achieve what we aim for. we shoudl proably add this to the ptg and or create a blueprint/spec to supprot this. i really dont think it shoudl be contovial to make pxe booting a nova instance form a server on the neutron netwrok simpler
On 22/10/2025 14:24, Eugen Block wrote: the question is how to opt into it.
my perfence is a neuton port extion to set boot priority on the port and make nova respect that and generate the correct xml
but im open to other options.
it woudl be good to get wider input.
perhaps a topic for a nova-neutron cross project session?
I was looking to test this before posting but I may not be able to get to it for a while. in 2014 there was https://blueprints.launchpad.net/nova/+spec/boot-order-for-instance This looks to have had some work done on it in https://review.opendev.org/c/openstack/nova-specs/+/133254 So someone intended to have this work but I have not done enough to prove that it works. -- Alvin Starr || land: (647)478-6285 Netvel Inc. || home: (905)513-7688 alvin@netvel.net ||