OVN has a special vtep port type which is used by OVN to configure top-of-rack switches. When a vtep port is added to an OVN logical switch, the ovn_controller_vtep daemon configures the switch via OVSDB to bind a physical port to a logical switch (tenant network).
Neutron already has support for this VTEP port type
by specifying the "vtep-logical-switch" and "vtep-physical-switch" parameters int he port binding profile: https://github.com/openstack/neutron/blob/8cba9a2ee86cb3b65645674ef315c14cfb261143/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py#L327
This RFE proposes that we add these two additional fields to the local_link_connection schema for a baremetal port. For the neutron interface, these fields will be passed through to neutron.
We have completed a PoC of this workflow and the end result is the ability for baremetal ports to be bound to tenant networks (even vxlan) without requiring any custom ML2 development. In addition, the movement of the baremetal port across the provisioning/cleaning/tenant network is handled gracefully.
In case it's not clear I plan on working on and submitting a bug against this RFE if the proposal is accepted.