This example does not preclude other queues from accessing those nodes. One solution is to use some other generic attribute with all other nodes and queues.
TORQUE does not currently provide a simple mechanism for mapping queues to nodes. However, schedulers such as Moab and Maui can provide this functionality.
The simplest method is using default_resources.neednodes on an execution queue, setting it to a particular node attribute. Maui/Moab will use this information to ensure that jobs in that queue will be assigned nodes with that attribute. For example, suppose we have some nodes bought with money from the chemistry department, and some nodes paid by the biology department.
|
$TORQUE_HOME/server_priv/nodes: node01 np=2 chem node02 np=2 chem node03 np=2 bio node04 np=2 bio qmgr: set queue chem resources_default.neednodes=chem set queue bio resources_default.neednodes=bio |
This example does not preclude other queues from accessing those nodes. One solution is to use some other generic attribute with all other nodes and queues.
More advanced configurations can be made with standing reservations and QoSes.
Related topics
© 2012 Adaptive Computing