-
Notifications
You must be signed in to change notification settings - Fork 19
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
add connection establish check for resource pool elements #258
add connection establish check for resource pool elements #258
Conversation
@@ -65,11 +65,13 @@ func (i *resourcePoolClient) Request(ctx context.Context, request *networkservic | |||
oldPCIAddress := request.GetConnection().GetMechanism().GetParameters()[common.PCIAddressKey] | |||
oldTokenID := request.GetConnection().GetMechanism().GetParameters()[TokenIDKey] | |||
|
|||
isEstablished := request.GetConnection().GetNextPathSegment() != nil |
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.
Is this fine for the restart scenario?
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.
@denis-tingaikin this is a good point, this check is just to provide do-nothing
op for refresh/heal connection requests. yes, the connection state must be recovered for forwarder restart scenario, is there a way nsm mgr set isRecovery
flag in connection object which would be parsed in forwarder chain elements to recover the state ? does sdk-vpp somehow do it already ?
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.
I suppose that in restart scenario we will have Connection.Path
cleaned up on NSMgr.
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.
Usually for checking to see if a particular chain element has already done its work for a connection I will check some metadata for the connection that gets set after the work has been done... since the real question is "Do I have to do work or not" that may be the best choice.
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.
@edwarnicke as discussed resource pool chain elements are now made to use vfconfig metadata cache (this is populated by same chain element) for isEstablished check. this would cover both restart and refresh scenarios.
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@est.tech>
b0a816f
to
12c08ff
Compare
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@est.tech>
12c08ff
to
a392587
Compare
…k-sriov@main PR link: networkservicemesh/sdk-sriov#258 Commit: ea35b0f Author: Denis Tingaikin Date: 2021-09-15 11:36:26 +0300 Message: - Merge pull request #258 from Nordix/resource-reestablish-check Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
…k-sriov@main PR link: networkservicemesh/sdk-sriov#258 Commit: ea35b0f Author: Denis Tingaikin Date: 2021-09-15 11:36:26 +0300 Message: - Merge pull request #258 from Nordix/resource-reestablish-check Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
…k-sriov@main PR link: networkservicemesh/sdk-sriov#258 Commit: ea35b0f Author: Denis Tingaikin Date: 2021-09-15 11:36:26 +0300 Message: - Merge pull request #258 from Nordix/resource-reestablish-check Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
…k-sriov@main PR link: networkservicemesh/sdk-sriov#258 Commit: ea35b0f Author: Denis Tingaikin Date: 2021-09-15 11:36:26 +0300 Message: - Merge pull request #258 from Nordix/resource-reestablish-check Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Signed-off-by: Periyasamy Palanisamy periyasamy.palanisamy@est.tech