Recipes.ENRT: add GeneveIpsecOvsTunnelRecipe #421
Merged
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
olichtne
force-pushed
the
geneve-on-ipsec
branch
2 times, most recently
from
4e44425 to
b15d4be
Compare
olichtne
force-pushed
the
geneve-on-ipsec
branch
4 times, most recently
from
b135083 to
52494b7
Compare
olichtne
changed the title
olichtne
force-pushed
the
geneve-on-ipsec
branch
from
52494b7 to
5280f14
Compare
Collaborator
Author
|
internal tests in beaker:
|
olichtne
force-pushed
the
geneve-on-ipsec
branch
from
5280f14 to
87c980b
Compare
Collaborator
Author
|
after a couple of rounds of testing internally, the final good results are here:
this is ready to be merged |
jtluka
requested changes
Dec 1, 2025
Collaborator
jtluka
left a comment
jtluka
left a comment
There was a problem hiding this comment.
Just minor issue and clarification.
Implements a new recipe that relies on openvswitch-ipsec service to encrypt any geneve traffic with ipsec. This recipe will be used for performance testing so a basic set of hw config mixins is added. Signed-off-by: Ondrej Lichtner <olichtne@redhat.com>
olichtne
force-pushed
the
geneve-on-ipsec
branch
from
87c980b to
ed1f0fb
Compare
jtluka
approved these changes
Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Implementing a new recipe, it's based on the previous https://github.com/LNST-project/lnst/blob/master/lnst/Recipes/ENRT/GeneveOvsTunnelRecipe.py and https://github.com/LNST-project/lnst/blob/master/lnst/Recipes/ENRT/GeneveOvsNetnsTunnelRecipe.py recipes.
The point of the recipe is to use 2 ovs bridges (one external, one internal) where the internal bridges are connected via a Geneve bridge and any outgoing traffic is encrypted via ipsec.
The ipsec configuration is applied automatically via the openvswitch-ipsec service which needs to be started after the ovs ipsec configuration is set up on the internal bridge.
The scenario mimics real usecases from OCP and will be used with performance evaluation as well so a basic set of hw config mixin classes are used.
Tests