-
Notifications
You must be signed in to change notification settings - Fork 320
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
Refactor toolkit installer #990
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Evan Lezar <[email protected]>
Signed-off-by: Evan Lezar <[email protected]>
b1c8a90
to
15d6c5e
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.
Pull Request Overview
This PR refactors the toolkit installer to prepare for a future change where a single container image is used for the toolkit. Key changes include new implementations for collecting libraries and executables, creating wrappers for executables, centralizing artifact discovery, and removing deprecated container/toolkit files.
Reviewed Changes
Copilot reviewed 24 out of 24 changed files in this pull request and generated 2 comments.
Show a summary per file
File | Description |
---|---|
cmd/nvidia-ctk-installer/toolkit/installer/executables_test.go | Adds tests for verifying the wrapper rendering of executables. |
cmd/nvidia-ctk-installer/toolkit/installer/libraries.go | Implements library collection logic with symlink creation. |
cmd/nvidia-ctk-installer/toolkit/installer/installer.go | Provides the main installer logic including file copying and wrapper creation. |
cmd/nvidia-ctk-installer/toolkit/installer/executables.go | Implements executable collection and wrapper file generation via templates. |
cmd/nvidia-ctk-installer/toolkit/installer/artifact-root.go | Introduces an artifact root abstraction for locating libraries and executables. |
cmd/nvidia-ctk-installer/toolkit/configure.go | Installs and configures the NVIDIA toolkit configuration file. |
Other files (including mocks, directory creation, and tests) | Update mocks and tests to support the refactored installer logic while cleaning up deprecated code. |
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.
First pass looks good. will give it a try
@@ -0,0 +1,84 @@ | |||
/** |
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.
is there a reason this license header is different?
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.
Different from what? The reason is that these changes have been on a branch associated with #602 for some time and I am factoring them out. Will update the header.
@@ -0,0 +1,169 @@ | |||
/** |
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.
same question
772bc62
to
9255c9c
Compare
Since this is running in a contianer the contents of the /etc/nvidia-container-runtime/config.toml file is equivalent to the default config. This change makes it explicit. Signed-off-by: Evan Lezar <[email protected]>
9255c9c
to
dee62ca
Compare
Signed-off-by: Evan Lezar <[email protected]>
This change moves the generating of a toolkit config to a separate file. Signed-off-by: Evan Lezar <[email protected]>
dee62ca
to
9660137
Compare
These changes refactor the toolkit installer used from the toolkit contianer.
The goal is to prepare for ##602 where a single container image is used for the toolkit instead of multiple container images.