Avoid recreating flows for a connected switch when consistency check is enabled #126
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.
Currently, when a switch connect (or reconnects) to Kytos, flow_manager send a FLOW_MOD to reinstall all the stored flows, no matter how is the switch flow table.
If the switch flow table is empty, forcing the flows to be reinstalled is okay. However, if the switch still has the flows and reconnects, reinstalling them will impact the traffic being forwarded, will clear the statistics, and is waste of resources. Furthermore, with the recent consistency check routine, this should be handed over.
This PR changes the behavior of flow_manager to use the consistency check routine, when enabled, to recreate the flows when the switch reconnects to Kytos.
Fixes #115