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.
feat: customize R generation to include GPUs #3325
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
Uh oh!
There was an error while loading. Please reload this page.
feat: customize R generation to include GPUs #3325
Changes from all commits
120e4ceb148c3fdea9a08File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
I think, we should enforce kubebuilder validation for numProcPerNode>=1 here: https://github.com/converged-computing/trainer/blob/764a765a8f6a462bc84234a3f84270fe720acf09/pkg/apis/trainer/v1alpha1/trainjob_types.go#L266
and here:
https://github.com/converged-computing/trainer/blob/764a765a8f6a462bc84234a3f84270fe720acf09/pkg/apis/trainer/v1alpha1/trainingruntime_types.go#L228
cc @tenzen-y @astefanutti
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.
@vsoch Do you want to add validation for numProcPerNode in the followup PR?
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.
I think I had it before (in the first PR) but was asked to remove it because it’s part of the API as an annotation?
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.
What we do need to think about is a case that we have for the Flux Operator (that may not be dealt with well here). Often there is a desire to put the number of nodes, but just say "discover and use all of the cores that are found" and then you would do like:
Note that I don't have any
-nspecified. For the Flux Operator, I allowed this case when the user put tasks as 0. Is there any way we can support something similar? Is the only way some special envar that flags and triggers the condition (regardless of what the-nis) since the validation of >1 is in the spec?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.
Please open dedicated PR to introduce this kubebuilder validation, we need to ensure that
numProcPerNode >= 1If Flux can dynamically discover all available devices on the node, we can rely on this functionality when
numProcPerNodeis omitted.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.
Excellent! I did not know that was an option. Thank you!
Uh oh!
There was an error while loading. Please reload this page.