-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Introduction of new SriovDevice and Node types.
SriovDevice is used to identify and record all sr-iov capable nics across the cluster. End users can control the enable / disable / configuration of VF's of underlying hardware by interfacting with corresponding object. Once enabled, the configured VF's show up as normal PCI devices available for pass-through to workload VM's. Node type is just used to create an object corresponding to each node in the cluster and is used via the controller requeue mechanism to trigger recurring reconciles of the PCI and SRIOV enabled devices. node controller registration renamed sriovdevices crd to sriovnetworkdevices changes to naming of methods and objects handle changes to skip pcibridge devices during node reconcile drop unwanted imports fixed unit tests for pcidevice controller updated dapper to use downloads.opensuse.org, and fixed trivy ci failures minor change to status updates when sriov device is enabled changed test script copy VFList to allow override of default sysPciBus path for tests with umockdev renamed sriov handler based on codefactor report use /host/proc to query host network ns without host networking addition of validating webhooks and changes to sriov device status moved vm lookup to use lists rather than custom index removed duplicates from Dockerfile.dapper label pcidevices with sriov details, skip non pcidevice nics cleanup based on pr feedback moved NODE_NAME to env variable and cleaned up nodename key references added debug logging for pcidevices label lookup and sriov webhook
- Loading branch information
1 parent
7cfa4f2
commit a68f554
Showing
48 changed files
with
35,322 additions
and
199 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.