-
Notifications
You must be signed in to change notification settings - Fork 348
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
chore: deprecate job move within priority group #9585
Conversation
✅ Deploy Preview for determined-ui canceled.
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## job-queue-move #9585 +/- ##
==================================================
- Coverage 49.86% 44.07% -5.79%
==================================================
Files 1247 1086 -161
Lines 162293 149901 -12392
Branches 2887 2888 +1
==================================================
- Hits 80922 66066 -14856
- Misses 81200 83664 +2464
Partials 171 171
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
||
- Agent and Kubernetes Resource Manager: Jobs can no longer be moved within the same priority | ||
group. Update a job's priority via CLI command to move a job ahead, or behind, of another job. | ||
Visit :ref:`modify-job-queue-cli` for details. Deprecation was announced in 0.33.0. |
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.
- Agent and Kubernetes Resource Manager: Jobs can no longer be moved within the same priority group. To reposition a job, update its priority using the CLI. For detailed instructions, visit :ref:
modify-job-queue-cli
. This change was announced in version 0.33.0.
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.
note to self: adjust priority in CLI or webui
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.
added suggestion
Ahead: true, | ||
ResourcePool: j.ResourcePool(), | ||
}) | ||
return fmt.Errorf("action not supported - update priority to move job") |
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.
we should update the proto definition to no longer have these options
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.
If we leave it like this, we can have a more informative error message though right?
I was thinking we could leave it until the UI changes are done to actually remove the option.
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.
The UI and the API being removed should happen at the same time (as in the same release) so I don't think the error message is that relevant here
We should update the proto definition comments / mark it as deprecated in proto at the least so our API documentation is accurate
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.
The UI updates need to be prioritized. That could be in a future release. My understanding from product is that it was an acceptable trade-off.
I agree with marking the proto definition as deprecated.
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.
Shouldn't the UI happen removal happen first?
Can we just wait till the UI removal happens then?
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 don't think I understand what you're suggesting. Are you suggesting we shouldn't merge this PR until the corresponding front-end work is completed?
My understanding from previous conversations is that we were going to remove as much as possible from the backend, and leave it as a backlog task to update the front-end. https://hpe-aiatscale.slack.com/archives/C06GMG83ZE0/p1718311967982659?thread_ts=1718298903.798219&cid=C06GMG83ZE0
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.
That previous conversation is talking about a slightly different situation. The previous conversation assumed that Kubernetes would still support this feature and the backlog ticket is to grey out it for agentrm / slurm cases. This change now has removed the feature from all resource managers. I think there is a gap between having a button that only works in certain situations verse a button that never works.
Have we asked the frontend team if by the release would be a reasonable deadline for their work on this?
Ticket
RM-360
Description
Deprecate job move within the same priority group. Jobs can still be re-ordered via CLI command by updating their priority.
Test Plan
Checklist
docs/release-notes/
See Release Note for details.