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

gnsi/pathz: clarify rotation behaviour for ongoing gNMI subscriptions #143

Merged
merged 2 commits into from
Mar 6, 2024

Conversation

brianneville
Copy link
Contributor

The index.md is updated with a section covering the expected behaviour for ongoing subscriptions when a server
experiences a pathz policy change.

This commit also updates the pathz.UploadResponse value so that
it contains information about ongoing subscriptions and whether
they would experience different behaviour under the incoming policy. .pb.go files were regenerated.

@brianneville brianneville changed the title gnsi/pathz: clarify rotation behaviour for ongoing gNMI subscribers gnsi/pathz: clarify rotation behaviour for ongoing gNMI subscriptions Dec 15, 2023
pathz/index.md Outdated Show resolved Hide resolved
@brianneville brianneville force-pushed the gnsi-pathz-subscriptions branch from b92fde0 to a27f5ea Compare January 24, 2024 14:02
Copy link

@ncorran ncorran left a comment

Choose a reason for hiding this comment

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

The PR still doesn't account properly for devices that have a single central policy DB only, not (up to) one per subscriber... and/or devices that want to enforce a stricter security posture.

@marcushines
Copy link
Contributor

I think at this point to resolve the issue we should look at simply dropping the connections on rotation and just forcing the new policy to be applied (this really only applies to streaming methods)

@brianneville brianneville force-pushed the gnsi-pathz-subscriptions branch from a27f5ea to bc5f8a8 Compare February 27, 2024 15:34
@brianneville
Copy link
Contributor Author

I think at this point to resolve the issue we should look at simply dropping the connections on rotation and just forcing the new policy to be applied (this really only applies to streaming methods)

Sounds fine - I've update the PR so that this approach is referenced in the index.md, please take a look @marcushines @ncorran

Copy link

@ncorran ncorran left a comment

Choose a reason for hiding this comment

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

Approved from Cisco

@marcushines marcushines merged commit cfdd2d9 into openconfig:main Mar 6, 2024
2 checks passed
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