On 11/8/22 13:11, Lorenzo Bianconi wrote: > Rely on the following new actions in order to introduce affinity timeout > support to load-balancer sessions: > - commit_lb_aff > - chk_lb_aff > > Introduce the following tables in switch and router pipelines > respectively: > - S_SWITCH_IN_LB_AFF_CHECK > - S_SWITCH_IN_LB_AFF_LEARN > - S_ROUTER_IN_LB_AFF_CHECK > - S_ROUTER_IN_LB_AFF_LEARN > > In this way OVN is able to dnat connections received from the same client > to a given load-balancer to the same backend if received in the affinity > timeslot. > Please note load-balancer affinity support has scalability limitation > since we need to create a new logical flow per backend. > > Acked-by: Mark Michelson <[email protected]> > Signed-off-by: Lorenzo Bianconi <[email protected]> > ---
Looks good to me, just a small typo below. That can be easily fixed when applying the patch. Acked-by: Dumitru Ceara <[email protected]> [...] > lib/lb.c > diff --git a/ovn-nb.xml b/ovn-nb.xml > index f41e9d7c0..de0243a96 100644 > --- a/ovn-nb.xml > +++ b/ovn-nb.xml > @@ -1908,6 +1908,13 @@ > requests only for VIPs that are part of a router's subnet. The > default > value of this option, if not specified, is <code>reachable</code>. > </column> > + > + <column name="options" key="affinity_timeout"> > + If the CMS provide a positive value for > <code>affinity_timeout</code>, Typo: s/provide/provides > + OVN will dnat connections received from the same client to this lb to > + the same backend if received in the affinity timeslot. Max supported > + affinity_timeout is 65535s. > + </column> > </group> > </table> > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
