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.
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
[Feature] Added more logs when pushing flows,
force
option and retries #29[Feature] Added more logs when pushing flows,
force
option and retries #29Changes from 8 commits
5c9120e
0028473
2dc963c
6230b8f
a4aae2f
364378c
8a985c4
35ac2ff
cefb5a1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@viniarck another enhancement opportunity is: we should only request a flow_mod add when it is a new switch (or it was previously disabled before). The reason basically related to the fact the flow_manager should take care of reinstalling the flows once the switch reconnects. Currently, once a switch reconnects a new
kytos/topology.switch.enabled
event is generated (https://github.com/kytos-ng/topology/blob/master/main.py#L517-L530) and LLDP flows are requested again (even though they probably exists at the switch, if the switch only reconnected).For the
kytos/topology.switch.disabled
event (the else branch of the conditional above), then it makes sense to remove the flows.Let me know what you think and we can create an issue to handle this specific enhancement.
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.
@italovalcy for sure, agreed. It also minimizes the number of events. Let's go for it and map this. The only corner case that I can see would be if an operator is running
flow_manager
without the consistency check enabled (do you know if we'll ever has this case in prod?), and then their switch has a physical outage losing the flows installed and then reconnects, but that in practice might not ever happen if operators always have the consistency check enabled, since the pros outweigh tremendously any potential drawback (if any, unless there's a bug).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've captured it on issue #31, let's keep refining and evolving it there. Thanks, Italo.