Actions
Story #12574
closed
[API] Propagate priority of parent container to children
Start date:
11/30/2017
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
Story points:
1.0
Description
Propagate from the requesting container to children.
A committed container request's priority should be no less than the priority of its requesting container, if any. Priority should be updated when the requesting container's priority changes.
Updated by Tom Morris over 7 years ago
- Tracker changed from Bug to Story
- Subject changed from Propagate priority of parent job (a-c-r) to children to [API Server] Propagate priority of parent job (a-c-r) to children
- Description updated (diff)
- Story points set to 1.0
Updated by Tom Morris over 7 years ago
- Target version changed from To Be Groomed to Arvados Future Sprints
Updated by Tom Morris over 7 years ago
- Target version changed from Arvados Future Sprints to 2017-12-06 Sprint
Updated by Lucas Di Pentima over 7 years ago
- Assigned To set to Lucas Di Pentima
Updated by Tom Clegg over 7 years ago
- Subject changed from [API Server] Propagate priority of parent job (a-c-r) to children to [API] Propagate priority of parent container to children
- Description updated (diff)
Updated by Peter Amstutz over 7 years ago
- Related to Story #12552: When priority is equal, the children of an earlier-submitted workflow should run first added
Updated by Peter Amstutz over 7 years ago
- Status changed from New to In Progress
- Assigned To changed from Lucas Di Pentima to Peter Amstutz
Updated by Lucas Di Pentima over 7 years ago
Just one suggestion: how about renaming update_priority to something more descriptive, like propagate_priority or update_children_priority. The code LGTM. Thanks!
Updated by Anonymous over 7 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|4ea88c89b61931b2f588461d530b4fa7dcf7487d.
Actions