Thanks for the updated series Ales.
After thinking about it more, I agree that we can do without the
priority in the output of `ovn-nbctl lr-nat-list` on patch 2. Therefore,
for the whole series:
Acked-by: Mark Michelson <[email protected]>
On 5/29/24 11:56, Ales Musil wrote:
This series adds the ability to have extra match per NAT, this allows
the CMS to have more fine-grained control over the NAT action. At the
same time it allows to have "duplicate" NATs e.g. multiple SNATs for
the same logical_ip as well as multiple DNATs for the same external_ip.
There is also priority in addition to the match which controls the
evaluation order of the NAT with match, as the priority can be used
only in combination with match.
Ales Musil (3):
nothd: Unify the priority calculation for NAT flows.
nb: Add support for match and priority in NAT.
northd: Use the NAT match column.
northd/northd.c | 97 +++++++-------
northd/ovn-northd.8.xml | 31 +++++
ovn-nb.ovsschema | 8 +-
ovn-nb.xml | 15 +++
tests/ovn-nbctl.at | 220 +++++++++++++++++++++---------
tests/ovn-northd.at | 79 +++++++++++
tests/system-ovn.at | 272 ++++++++++++++++++++++++++++++++++++++
utilities/ovn-nbctl.8.xml | 14 +-
utilities/ovn-nbctl.c | 189 ++++++++++++++++----------
9 files changed, 736 insertions(+), 189 deletions(-)
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
