Thanks Lorenzo, a few suggestions from my side.
On Thu, May 18, 2023 at 10:20:34PM +0200, Lorenzo Bianconi wrote: > In the current codebase for distributed gw router port use-case, > it is not possible to add a load balancer that redirects the traffic > to a backed if it is even the internal IP of a FIP NAT rule since s/backed/back-end/ s/even// ? > the reply traffic is never centralized. Fix the issue centralizing the > traffic if it is the reply packet for the load balancer. > > Reported-at: https://bugzilla.redhat.com/show_bug.cgi?id=2023609 > Signed-off-by: Lorenzo Bianconi <[email protected]> ... > diff --git a/northd/ovn-northd.8.xml b/northd/ovn-northd.8.xml > index 7da912da3..1703d8bae 100644 > --- a/northd/ovn-northd.8.xml > +++ b/northd/ovn-northd.8.xml > @@ -4452,6 +4452,22 @@ icmp6 { > </p> > > <ul> > + <li> > + For all the configured load balancing rules that includes an IPv4 maybe: s/includes/include/ > + address <var>VIP</var>, and a list of IPv4 backend addresses > + <var>B0</var>, <var>B1</var> .. <var>Bn</var> defined for the > + <var>VIP</var> a priority-200 flow that matches <code>ip4 && maybe: s/flow/flow is added/ ? > + (ip4.src == <var>B0</var> || ip4.src == <var>B1</var> || ... > + || ip4.src == <var>Bn</var>)</code> with an action <code> > + outport = <var>CR</var>; next;</code> where <var>CR</var> is the > + <code>chassisredirect</code> port representing the instance of the > + logical router distributed gateway port on the gateway chassis. > + If the backend IPv4 address <var>Bx</var> is also configured with > + L4 port <var>PORT</var> of protocol <var>P</var>, then the match > + also includes <code>P.src</code> == <var>PORT</var>. > + Similar flows are addeded for IPv6 counterpart. maybe: s/counterpart// > + </li> > + > <li> > For each NAT rule in the OVN Northbound database that can > be handled in a distributed manner, a priority-100 logical ... _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
