UI: Server-side reschedule tracking #4254
Conversation
layers.svg from Open Iconic
For when the icon should be less prominent than the content around it
An open layout that makes its contents feel less cramped. Useful for large visualizations.
Useful for actions, icons, and checkboxes
Intended to be used in a timeline view.
| @@ -23,4 +23,6 @@ export default Model.extend({ | |||
| job: belongsTo('job'), | |||
|
|
|||
| modifyIndex: attr('number'), | |||
|
|
|||
| waitUntil: attr('date'), | |||
There was a problem hiding this comment.
Do you want this as a string and then parse it out when you need to use it? Fine if the answer is "no", just wanted to call out that date parsing on models is (unless they changed that recently) eager (which could be totally fine here).
There was a problem hiding this comment.
I've been trying to do the things the expected way until it becomes a problem. Since evaluations don't get loaded by the thousands, I think this is okay here.
| import shortUUIDProperty from '../utils/properties/short-uuid'; | ||
|
|
||
| export default Fragment.extend({ | ||
| allocation: fragmentOwner(), |
There was a problem hiding this comment.
huh TIL about fragmentOwner
| // the time (precise to ms) as a date, and store the remaining ns | ||
| // as a number to deal with when it comes up. | ||
| hash.TimeNanos = hash.RescheduleTime % 1000000; | ||
| hash.Time = Math.floor(hash.RescheduleTime / 1000000); |
|
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Nomad 0.8 introduced the ability for Nomad to automatically reschedule allocations on different nodes in an effort to get jobs running in the event that it's not the job artifact, but the node that is faulty.
Now the UI has the ability to track all the times allocations were automatically rescheduled.
Allocation rows are marked with an icon to denote that it has already been rescheduled
The allocation detail view shows a timeline of all reschedule events prior to the allocation
If Nomad gives up rescheduling (based on the reschedule stanza in the job spec) the UI will report that too
Clicking through allocations will update the timeline and always show the next allocation when not viewing the last reschedule
When viewing the reschedule events timeline while rescheduling is still occurring, the UI will automatically update with the next allocation once it's scheduled and the amount of time remaining before scheduling when Nomad is intentionally delaying
