Define a max wait time for the task to start out of the scheduling queue else skip the task. This will ensure that tasks don't start past the end of the change window for the operation.
Below was the original idea, but evolved to above:
Currently our NA system has a following property set:
scheduler/serialtaskadminrestrictedpriority = 4
We would like an option to bind a certain task type to a certain priority. In our case, we want to bind the "Reboot Device" task to priority 1.
We think that the only two tasks for which it makes sense to run in serial are "Update Software" and "Reboot Device".
Our regular scheduled tasks are running with priority 5, so normally the serial tasks ran with priority 4 will get in front in the queue and start running immediately.
However we face a potential problem if one of our Operators decides to manually run a serial task with priority 1,2 or 3. Then it will pause the execution of the reboot task, which could lead to an operational risk. We want a way to bind "Reboot Device" so it will always start with a priority 1, and no other task would be able to pause its progress and move in front of it in the queue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.