Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding the support of Linux bridge interface for VM setup #157

Closed
wants to merge 1 commit into from

Conversation

capolrik
Copy link
Collaborator

Use the --bridge option to create a NAD that will be attached to the VMs

Type of change

  • New feature

Description

Adding the support for bridge interface using VMs.
A NNCP needs to be defined before running the test to defined the linux bridge.
Then, the bridge name should passed to the option:

k8s-netperf --debug --vm --bridge br0

with the following NNCP

apiVersion: nmstate.io/v1alpha1
kind: NodeNetworkConfigurationPolicy
metadata:
  name: br0-eth1
spec:
  desiredState:
    interfaces:
      - name: br0
        description: Linux bridge with eno2 as a port
        type: linux-bridge
        state: up
        ipv4:
          dhcp: true
          enabled: true
        bridge:
          options:
            stp:
              enabled: false
          port:
            - name: eno2

Related Tickets & Documents

  • Related Issue #
  • Closes #

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.

Testing

On OCP 4.17,

k8s-netperf --debug --vm --bridge br0

and

k8s-netperf --debug --vm

Use the --bridge option to create a NAD that will be attached to the VMs
Copy link
Member

@jtaleric jtaleric left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does the user need to setup anything prior to running this? We might want to add some documentation.

@capolrik capolrik closed this Nov 14, 2024
@capolrik
Copy link
Collaborator Author

Sorry I got a versioning issue, let me re-open the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants