-
Notifications
You must be signed in to change notification settings - Fork 261
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
[backport 2.8] Add vGPU allocatable warning banner #11600
Conversation
shell/assets/translations/en-us.yaml
Outdated
@@ -1279,6 +1279,8 @@ cluster: | |||
macAddress: Mac Address | |||
macFormat: 'Invalid MAC address format.' | |||
vGpus: | |||
warnings: | |||
minimumAllocatable: It's highly recommended to select a vGPU with a number of allocatable devices greater then the number of nodes (Machine Count) to avoid "un-schedulable" errors after cluster updates. |
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.
Similar to feedback on the 2.10 & 2.9 related PRs:
then
should be thanvGPU
should be used with that capitalization for consistency
shell/assets/translations/en-us.yaml
Outdated
@@ -1279,6 +1279,8 @@ cluster: | |||
macAddress: Mac Address | |||
macFormat: 'Invalid MAC address format.' | |||
vGpus: | |||
warnings: | |||
minimumAllocatable: It's highly recommended to select a vGPU with a number of allocatable devices greater then the number of nodes (Machine Count) to avoid "un-schedulable" errors after cluster updates. | |||
errors: | |||
notAllocatable: '"VGPUs" not allocatable. There are not enough [{vGpus}] devices to be allocated to each node in machine pool [{pool}]' |
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.
vGPU not VGPU
@a110605 let us know if there's anything else for you to look at here since with Francesco out, we'll need someone else to merge. If you feel everything's OK based on your own concerns, then you can approve & merge. |
Hi @gaktive , the vGPU allocatable number in dropdown is introduced in PR #11399. Without #11399, the banner in this PR is meanless. As I synced with Franesco last time, this PR should wait for #11399 merge first. (correct me if I'm wrong) |
cb01f91
to
c0b51d4
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.
Need rebase after #12136 merge
- Add vGPU allocatable warning banner - Update shell/assets/translations/en-us.yaml - Fix wording - Show allocation warning only when allocation info are available Signed-off-by: Francesco Torchia <francesco.torchia@suse.com>
c0b51d4
to
47e5dd9
Compare
This is a backport for #11017
Fixes #11009