change capo to make default behavior configurable #753
Conversation
This file contains hidden or 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
hedibouattour
force-pushed
the
change-capo
branch
2 times, most recently
from
db291cf to
dea6958
Compare
hedibouattour
force-pushed
the
change-capo
branch
from
db8bf3c to
21b1011
Compare
This patch uses a vpp capo plugin patch that makes the default behavior when policies don't match configurable: drop, or goto profiles, depending on the existence of user defined policies This addresses the issue where dataplane takes wrong decisions because it isn't aware of the difference between a user defined policy and an implicit policy (like failsafe) This also prepends an explicit deny policy in the case of an empty hostendpoint (hep with 0 policies and 0 profiles). This also makes endpointtohost action prior to failsafe to comply with doc.
hedibouattour
force-pushed
the
change-capo
branch
from
21b1011 to
521cf48
Compare
Closed
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.
This patch uses a vpp capo plugin patch that makes the default behavior when policies don't match configurable: drop, or goto profiles, depending on the existence of user defined policies
This addresses the issue where dataplane takes wrong decisions because it isn't aware of the difference between a user defined policy and an implicit policy (like failsafe)
This also prepends an explicit deny policy in the case of an empty hostendpoint (hep with 0 policies and 0 profiles).
This also makes endpointtohost action prior to failsafe to comply with doc.