You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our workflow has us allocating jobs to a pool of queues (all maas servers with their own queue). As we have a pool of servers, we want to load balance the jobs if possible. Currently we can only see the length of the queue only after submitting a request. We then have to immediately cancel the job if the queue is too long. Also, the testflinger output only indicates how many jobs are queued. As a result, if the device is idle or in the middle of a job, the queue length is 0. There is no way to determine if the queue has active jobs that I'll end up having to wait on.
What would be helpful is a way to return the status of the queue and how many jobs are waiting. For example:
Our workflow has us allocating jobs to a pool of queues (all maas servers with their own queue). As we have a pool of servers, we want to load balance the jobs if possible. Currently we can only see the length of the queue only after submitting a request. We then have to immediately cancel the job if the queue is too long. Also, the testflinger output only indicates how many jobs are queued. As a result, if the device is idle or in the middle of a job, the queue length is 0. There is no way to determine if the queue has active jobs that I'll end up having to wait on.
What would be helpful is a way to return the status of the queue and how many jobs are waiting. For example:
The text was updated successfully, but these errors were encountered: