Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved recovery for policy base routing #598

Merged
merged 1 commit into from
Jul 8, 2023

Conversation

ljkiraly
Copy link
Contributor

@ljkiraly ljkiraly commented Jul 5, 2023

Related issue: networkservicemesh/deployments-k8s/issues/9463

Fix for faulty ip rules after forwarder restart
Using proper key in internal Map for routing table IDs; Ensure that the routing table belongs to the link handled by NSM; At policy recovery do not flush the routing table if more than one rule reffering to it,
deleting the last rule with reference to a given routing table will flush the table.

@ljkiraly ljkiraly force-pushed the pbr-sync-table-key branch from 7587ee6 to 8a9f7c9 Compare July 5, 2023 14:16
Related issue: networkservicemesh/deployments-k8s/9463

Fix for faulty ip rules after forwarder restart
Using proper key in internal Map for routing table IDs;
Ensure that the routing table belongs to the link handled by NSM;
At policy recovery do not flush the routing table if more than one rule reffering to it,
   deleting the last rule with reference to a given routing table will flush the table.

Signed-off-by: Laszlo Kiraly <laszlo.kiraly@est.tech>
@ljkiraly ljkiraly force-pushed the pbr-sync-table-key branch from 8a9f7c9 to 6a9ccb5 Compare July 5, 2023 14:22
@szvincze
Copy link

szvincze commented Jul 6, 2023

Hi @denis-tingaikin, @edwarnicke,

Now this issue is a highest priority one for us and because of the time pressure it is not an option to wait for NSM v1.10.0 release. Thus, we are planning to use a fork that contains the very same fix on top of NSM v1.9.0. Due to this reason it would be crucial to have it reviewed as soon as possible to be able to backport the final version that will be part of the coming NSM release, to keep it compatible for the future upgrade.

Can you please prioritize the review of this fix?
Thanks in advance.

@ljkiraly ljkiraly requested a review from LionelJouin July 6, 2023 13:51
Copy link
Member

@denis-tingaikin denis-tingaikin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@szvincze sure!

@glazychev-art Could you aslo have a look?

@ljkiraly ljkiraly requested a review from glazychev-art July 6, 2023 14:23
@denis-tingaikin denis-tingaikin merged commit 891e1f8 into networkservicemesh:main Jul 8, 2023
nsmbot pushed a commit to networkservicemesh/sdk-sriov that referenced this pull request Jul 8, 2023
…k-kernel@main

PR link: networkservicemesh/sdk-kernel#598

Commit: 891e1f8
Author: Denis Tingaikin
Date: 2023-07-08 03:09:54 +0300
Message:
  - Merge pull request #598 from Nordix/pbr-sync-table-key
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/cmd-nse-l7-proxy that referenced this pull request Jul 8, 2023
…k-kernel@main

PR link: networkservicemesh/sdk-kernel#598

Commit: 891e1f8
Author: Denis Tingaikin
Date: 2023-07-08 03:09:54 +0300
Message:
  - Merge pull request #598 from Nordix/pbr-sync-table-key
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/sdk-vpp that referenced this pull request Jul 8, 2023
…k-kernel@main

PR link: networkservicemesh/sdk-kernel#598

Commit: 891e1f8
Author: Denis Tingaikin
Date: 2023-07-08 03:09:54 +0300
Message:
  - Merge pull request #598 from Nordix/pbr-sync-table-key
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
@denis-tingaikin
Copy link
Member

Merging this since its ASAP

@glazychev-art feel free to add comments and we could resolve them in the separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants