Comment 11 for bug 1931244

Terry, while I'd love it if Neutron had completed the migration to using OVN services and database for everything as a replacement for the AMQP RPC and agent infrastructure, the reality is that this is not (yet) the case.

For the SR-IOV use case the OVN driver owns ports and provides DHCP- and Metadata- services to the consumers of the sriovnicsiwtch mechanism driver. At this point in time the sriovnicswitch driver still relies on an agent and RPC.

The RPC code does indeed read and update ports and subsequently will call into the OVN driver.

Thank you for the pointer to the RpcWorker class name. I will put up a proposal for how we could conditionally add OVN IDL connections to the RPC Workers gated on the presence of the sriovnicswitch driver.