The current system does not allow users queuing jobs on systems they have no permissions for. One has to loan the machine first, which is not what we want in such case. When the job ends the user could (and often will) forget to return it. Adding approvals to beaker would enable queuing such a jobs: - jobs would remain in the queue until approved - owner would get notified on any such request and could Approve/Deny access - user would get notified after Owner A/D the access - on deny the job would be marked cancelled with Owner's comment Add a field for justification of request. This will help keep track why's the system in use by unauthorized person.
Approvals should be optional per system and requester: - people in these groups will {always/never} require approval - systems in these groups will {always/newer} require approval - systems in certain group will {always/never} require approval for people in following groups:...
Bulk reassignment of issues as Bill has moved to another team.
We have no current plans to support a queue with manual intervention for third party system access. Instead, we plan to implement a more flexible prioritization system that allows system owners to grant access to other users, while still allowing jobs from the appropriate groups to have higher priority. See http://beaker-project.org/dev/proposals/effective-job-priorities.html for more details.