[Fix] Adjust MEF E-Line tests to also consider failover_path flows #144
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.
This PR is related to kytos-ng/mef_eline#175
Description of the change
With the introduction of the failover path on fully dynamic EVCs (those in which
dynamic_backup_path = True and not primary_path and not backup_path
), the number of flows in the flow table grew a bit. Thus, some end-to-end tests had to be adjusted accordingly.The basic idea of the failover path is described in EP029, but below is the important part that impacts this PR:
The takeaway from the above description is basically: switches that are UNIs will have an extra flow for the failover path (the egress flow, which is pre-installed -- just for information: during a failure, the ingress flow will be then installed); switches that are in the path will have two extra flows for the failover path (the entire path is pre-installed).
In summary, this PR adjusts the tests that create fully dynamic EVCs to consider the aforementioned extra flows.
Results of the execution of the end-to-end tests (together with MEF E-Line's failover branch) can be seen below: