Description of problems: 1) When using SRIOV in OVN we need to deploy Neutron DHCP agents to capture the DHCP requests from the instances on the controller nodes. If DHCP agents are deployed on HA, it means that 3 DHCP ports will be created. Currently, networking-ovn expects only 1 DHCP port per network to serve metadata and it won't work as it is right now [0]. We shall reuse one of those DHCP ports for the distributed OVN metadata of non SRIOV instances. 2) Even after 1) is fixed, SRIOV instances won't be able to reach the local metadata services on compute nodes since the requests will skip the hypervisor. We should enable Neutron Metadata Agent on these deployments as well as the isolated metadata case for the DHCP so that metadata is served through the controller/network nodes. [0] https://github.com/openstack/networking-ovn/blob/5.0.0.0b3/networking_ovn/common/ovn_client.py#L1510
As discussed in the squad meeting, we'll first go with config drive for serving metadata in SRIOV deployments (this way we won't deploy Neutron metadata agent). In the future we can look at how to deploy OVN metadata agent in controllers also for the SRIOV case. A fix is still needed in networking-ovn to handle multiple ports.
We merged this patch [0] to support both neutron dhcp agent ports and metadata ports. I'll do the backport to 13 [0] https://review.openstack.org/#/c/620860/
Blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1683568
(In reply to Eran Kuris from comment #8) > Blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1683568 Hi Eran, why would this BZ blocked by the support of 'flat' networks ?
Oh ok was a confusion as Lucas changed the title of BZ 1683568, it's blocked due to the support of both 'flat' and 'vlan' tenant networks. Now I get it. Technically we could verify this independently by booting a VM on a provider network, right?
(In reply to Daniel Alvarez Sanchez from comment #10) > (In reply to Eran Kuris from comment #8) > > Blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1683568 > > Hi Eran, why would this BZ blocked by the support of 'flat' networks ? Hi Daniel, As you mentioned in comment 11 the title was changed. This bug is blocked by the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1673027 Yes, we can deploy OVN -SRIOV setup with a workaround and verify this bug but we don't do that because it's not the right process.
SRIOV is not supported in OSP13, should be supported starting OSP16, see bug 1666684.