The tasks of a UNICORE job consume resources on the execution system. This may be the use of an application, or certain number of nodes for a parallel job, or some available storage. On the other hand, each UNICORE site imposes certain resource limitations on the tasks. They reflect more or less the capabilities of the batch queuing systems on the target systems. The resource editor is used to combine both requirements to formulate the requests of the tasks and to compare this against the limits from the Vsites.
The resource editor is opened by selecting "Resources" from the Job Group panel: Actually it has an editing and managing funcitonality where the latter is restricted to the tasks in a job group. Therefore the list of tasks, which is presented in the lower half of the panel, depends on the selection of a job group (in the example below: PrimaryGroup) in the Job Preparation tree.
If a job is constructed from scratch, all tasks of a selected job
group carry initially the Site Defaults resource set which means that
the default values provided by the Vsite are used for execution of
the tasks. To define specific requests a new resource set has to be
created by pressing the
button. This will open a new panel where the resource limits of the
current Vsite (selected for the job group) are presented together
with a Request column for the actual requirements. The rows in this
table can be enabled individually, all disabled rows use implicitly
the values of the Default column. The required values are directly
compared against the limits, and marked either green or red depending
on the outcome of the value check. The client will refuse to submit a
job with incorrect resources. When loading a job from disk or when
changing the Vsite of a job the resource settings are checked
automatically.
New resource sets are listed in the upper part of the managing panel with their (editable) names. To assign a resource set to one or more tasks, it has to be selected first. Then, all tasks which shall be bound to this resource set, have to be selected in the Tasks part of the panel. The successful assignment is indicated by the name of the resource set in parentheses.
By repeating this procedure a task can be rebound to different
resource set. Or it can be reset to the initial state by assigning
the Site Defaults with the
button.
If a resource set is edited after assigning it to several tasks, these tasks will all run on the Vsite with the updated resource set! The assignment has to be understood as a linkage of objects (resource set and tasks).
NB: the new values of a resource set are only valid for the tasks in the current job group! If in another job group a resource set with identical name is used, these resource sets are nevertheless totally independent of each other.
|
|
Resource sets can be stored and loaded to and from disk. This make it possible to store predefined resource templates, e.g. for SMP systems or vector machines. The following list explains the functionality of the buttons in the resource editor. This information is also presented as tool tip if you move the mouse over the buttons.
|
|
Add a new resource set |
|
|
Load a resource set from file |
|
|
Save a resource set to file |
|
|
Save a resource set using a new filename |
|
|
Edit selected resource set |
|
|
Remove selected resource set from list |
|
|
Select all tasks |
|
|
Set selected tasks to site default resources |