Description of problem: Jeff Burke reported that the order in which the scheduler finds machines is too limited. In that it tries machines you own, in your group and then the general pool. To get around this Jeff kicks of jobs to fill the owner & group machines and then one more to get into the general pool. Then he cancels the owner & group jobs. Obviously not efficient. Alternative: Allow the job submitter to state the order they want their jobs to be scheduled in. In most cases the UI can suggest sensible defaults. For example, much like the UI interface for adding search terms, users could add groups to a list that sets the order they'd like the scheduler work in. This /may/ be the default order My Machines My Group Machines General Pool But permit the user to change it to anything General Group A Group B My Group Machines My Machines
Bulk reassignment of issues as Bill has moved to another team.
This will be addressed as part of the System Pool design in Beaker 1.1 (see http://beaker-project.org/dev/proposals/system-pools.html#prefer-particular-system-pools-for-recipe-execution)
This is on hold until we evaluate the possibility of switching to a more capable scheduling engine.