Bug 805006
Summary: | [RFE] add group priorities | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Vladimir Benes <vbenes> |
Component: | scheduler | Assignee: | Nick Coghlan <ncoghlan> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 0.8 | CC: | bpeck, cmeadors, dcallagh, llim, mcsontos, rmancy, stl |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | GroupModel | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-15 08:42:23 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: |
Description
Vladimir Benes
2012-03-20 12:29:19 UTC
Specifying <group op="!=" value="GROUP_TO_EXCLUDE"/> works for me to avoid using machines with special-HW from one group to be used for tasks which: - could run on anything and/or - belong to other group This often results in longer wait time for me, but is believed to increase the universe happiness sum. Bulk reassignment of issues as Bill has moved to another team. For Beaker 1.1, we should be implementing the concept of "System Pools", which will allow this behaviour to be controlled through a different mechanism. |