-
Notifications
You must be signed in to change notification settings - Fork 205
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
Restructure CDI use with plugins #1810
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How moving CDI spec generation (from generic looking deviceplugin/server.go
) to fpga_plugin.go
, makes CDI use more generic?
It allows the plugins (or their initcontainers) to generate the full spec rather than being limited to a subset (hooks) of the functionality. |
8ee3530
to
7d333b7
Compare
975f54d
to
8625c5a
Compare
9ff8504
to
f950803
Compare
04c8549
to
51d464b
Compare
@bart0sh please review again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Pass the whole cdi.spec structure to DeviceInfo and use cdiCache for interacting with the CDI files on the host. Signed-off-by: Tuomas Katila <[email protected]>
51d464b
to
c3a01b9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Restructure CDI use with plugins. Allow passing the whole CDI spec from plugin to server.