[th/mrvl-vsp-dp-rework] Marvell VSP: Add configurable MAC learning for OVS data plane #611
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.
Add isMacLearning parameter to control bridge switching behavior. When true, configures highest priority NORMAL flow for MAC-based learning. When false, allows traffic routing through network functions.
This takes the first patch of #562 so we can merge that part.
It works fine, but note that in our Marvell CI system (Jenkins job 99_E2E_Marvell_DPU_Deploy), we skip NF tests via
export SKIP_NF_TESTING=true, so we don't actually test this change in that CI system.The problem is, that the related tests under
e2e-test/e2e-test.gohave a hard-codedEXTERNAL_CLIENT_DEV=eno12409, which is not correct on the system with our Marvell CI (there the corresponding interface is calledeno2).We should fix that separately (https://issues.redhat.com/browse/MDC-132). On #562 there is also a patch
e2e-test: Removed skipNetworkFunctionTesting Option from e2e-test to test Marvell VSP Default DP With NF.which would dropSKIP_NF_TESTING=true. But we cannot do that without first addressing the issue of hard-codedEXTERNAL_CLIENT_DEV=eno12409. A potential solution could be #579, or something else entirely. That patch should be picked up later.But the problem with the CI should not block this patch.
CC @alkama-hasan