-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Merge in dev for the upcoming 0.3 release #109
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…strings Using the newly introduced roto concepts, this adds: * a first few constants (for well-known communities) * a Context comprised of the Log OutputStream * new logging based on Strings, for which many formatting helpers are added on the BgpUpdate/BmpMsg/RotondaRoute roto types. And everything is properly docstringed now.
With this commit, a first simple helper is added to the ingress Register to find 'related ingresses'. In this case, an MRT updates file is likely to be processed after an MRT RIB dump is ingested. At that point, the ingress Register is populated with BGP sessions to which the updates in the subsequent MRT files pertain.
Assuming that one mrt-file-in unit processes files from only a single vantage point, we register the unit in the ingress register and use its ingress_id when matching/registering anything from files processed by this unit. That way the unit will not touch a seemingly similar sessions (in terms of remote peer+asn) from other vantage points.
As the bmp-in unit does not store anything anymore (the RibUnit takes care of all that), the stored_prefix metric does not make sense anymore.
…ut and mrt-file-in units
density215
approved these changes
Jan 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.