[trim]
I think until ml2/ovs is part of the tree (and I don't think it will be booted any time soon), DHCP agent is just a must. There are also some (BM iPXE?) use cases that require a DHCP agent even with ml2/ovn at the moment. (Though we are on the lookout to reduce the number of these special scenarios.)
I suspect you mean, until it is removed (which I also don't think will be any time soon (but a user context exchange during a ptg session is likely going to be helpful here overall to Neutron developers/maintainers)).
As an FYI, OVN has support for iPXE, however iPXE is on a path to decline. Secure Boot use mandates are hindering iPXE's continued use in regulated environments. The future forward path from the Ironic community point of view as it relates to network booting is HTTPBoot. HTTPBoot requires slightly different records and a specific user class response which we can set with dnsmasq via neutron-dhcp-agent today. We (in Ironic) have not explicitly explored doing the same with OVN due to capacity constraints *and* the known list of issues with OVN. Happy to elaborate more, but just wanted to provide some base context to help facilitate discussion later.
It looks like Brian just replied about scheduling a session. I'm sure we can get into the fine details then.
Thanks everyone!
[trim]