-
Notifications
You must be signed in to change notification settings - Fork 9
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
NSM connection (VIPs and routes) update in TAPA #178
Conversation
What version of NSM is required? Not v1.2.0 I assume? |
It requires the latest version in the main branch of the nsmgr and forwarder-vpp + this PR: networkservicemesh/sdk-kernel#433. Also, the NSM dependencies of Meridio must be updated (will be done in a separate PR when NSM 1.3 will be available). |
* The initial NSM request does not contain any information about the ip context. Once the conduit connected (sucessful NSM request), the VIP watcher will call SetVIPs which will update (new request) the NSM connection (SrcIPs and policies). * the initial SrcIPs are saved in the conduit struct (to not mix the target IPs and VIPs) * The previous code has been removed
* The last privileges required (NET_ADMIN) has been removed
I rebased master, NSM has been uplifted and all PRs requireed are merged. |
Can't say much about the code since my NSM knowledge is limited but I have applied this PR, built and tested and it seem to work fine. The |
vipsSlice = append(vipsSlice, vip) | ||
var err error | ||
// update the NSM connection | ||
// TODO: retry if error returned? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe nsm's retry client could come handy here
The initial NSM request does not contain any information about the ip context. Once the conduit connected (sucessful NSM request), the VIP watcher will call SetVIPs which will update (new request) the NSM connection (SrcIPs and policies).
The initial SrcIPs are saved in the conduit struct (to not mix the target IPs and VIPs).
The previous code has been removed.
The last privileges required (NET_ADMIN) has been removed.
issue: #164
related NSM issues:
Changes required before merging: