Bug 622439
| Summary: | [RFE] Waiting in line functionality | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | David Kovalsky <dkovalsk> |
| Component: | scheduler | Assignee: | beaker-dev-list |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 0.5 | CC: | benl, bpeck, cbouchar, mcsontos, qwan, tools-bugs |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | GroupModel | ||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-19 22:26:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 593663, 790243 | ||
Hi David, from what I can tell something like this seems warranted. I think notifying the user that other people are queuing for their machine might be a good idea. I'm not sure about an 'urgent' priority check. I wonder if this would be subject to abuse. Hey Raymond, I wouldn't be too worried about abuse. In fact, sending a private email is much more prone to the "I need it now" to abuse than having the information visible in public :) Another good thing about the public waiting queue is that it's easier to prioritize who will get the system next. And in the end, it's up to the holder of the machine if (s)he will give it up anyway. Bulk reassignment of issues as Bill has moved to another team. *** Bug 629902 has been marked as a duplicate of this bug. *** The updated usage reminder emails in Beaker 0.18 (see https://beaker-project.org/dev/proposals/beaker-usage-report-emails.html) cover some aspects of this, in that owners of reserved systems will be reminded daily if queued recipes are waiting for those systems. |
Often times we have only 1 "special" type of system in inventory that more groups want to get their hands on. Especially in the snapshot phase, where the schedule is tight. As it is right now, the workflow is see who holds the system and chase him down (IRC, mail, personally), which doesn't scale with more requestors. I'd like to see some "standing in line" feature. First show at how I image it: 0) somebody is holding a system with unique storage that I need 1) I try reserving a system, but get put into the queue, because someone else has it. 1a) I manually signal (comment, priority) that I need the system quickly 1b) other people can do that too 2) Owner of the system gets email notification that someone else urgently needs the system he/she is holding. 2a) Queue of requestors in urge is easily visible in Inventory Web UI.