On 2/12/25 23:48, Ilya Maximets wrote: > > One more thing is that we should add an extra lower priority flow that > will not match on the network id, but will directly use the first network > for SNAT: > > stage:S_ROUTER_OUT_SNAT > priority:100
105 might be a better priority for this, as there are other flows in this stage at 100 (the ones for lb_force_snat_ip=<some actual ip>). > match: flags.force_snat_for_lb == 1 && ip4 && outport == X > actions: ct_snat(lrp_networks.ipv4_addrs[0]); > > This is useful for upgrade scenarios, or in case this change is going to > be backported. If northd is upgraded first, older ovn-controller that > doesn't recognize network_id flag will not install flows that use it, but > it will install this one and will have old behavior of SNATting to the > first IP working, until upgraded. > It is not a correct upgrade order, but if we want to beckport this change, > then it becomes reasonable as we do not enforce upgrade order for minor > release updates. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
