Hi Sergey, The LB support for HW VTEP is not implemented. The main trouble is the fact that HW VTEP device itself cannot modify packets or do whatever with control plane traffic (answer ARPs, etc.). At least for now.
Additional L3 Gateway chassis can be used to connect routed overlay topologies with HW VTEP. In this case L3 GW chassis will answer ARP requests for overlay GW IP for “vlan” side arriving requests and route packets to another subnets. This is an asymmetric routing: ingress traffic (from outside into OVN) goes from HW VTEP chassis to L3 GW chassis and next to destination VM’s/container’s chassis (hypervisor). On the reverse direction traffic goes directly from this hypervisor to HW VTEP skipping L3 Gateway. So in load balancing case L3 Gateway could be the chassis which does the load balancing, but we must make reply traffic going via this L3 GW for “unDNATing”. This is not implemented yet, thus load balancing stage is skipped in logical switch pipeline for packets coming from HW VTEP. Hope, this answers your question. regards, Vladislav Odintsov > On 20 Dec 2023, at 07:12, Sergey via discuss <ovs-discuss@openvswitch.org> > wrote: > > Hello! > > We are using the OVN HW-VTEP mechanism with our OpenStack > installation, and it works great. > But we are testing LB (Load Balancer) now, and it does not work in the > case of this kind of network. > > According to documentation and code: > https://github.com/ovn-org/ovn/blob/v23.09.1/northd/northd.c#L6996 > All tables about LB are skipped in the case of HW-VTEP, it goes > directly to table 17. > > My question is, is it reasonable? > Or does it have to be fixed? > _______________________________________________ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
