-
Notifications
You must be signed in to change notification settings - Fork 3
Resources
As the name implies, a hostgroup is a collection of cluster nodes in Grid Engine. Hostgroups can be used to group together hosts for any reason, such as hardware capabilities, or system sponsor. In our case, we're using them to divide systems up based on their sponsor (owner).
qconf -shgrpl
qconf -shgrp @mesa
Using the qconf utility, create a new hostgroup named "@mesa". The utility will then open the default EDITOR, presenting a config file.
qconf -ahgrp @mesa
Example of a hostgroup configuration:
group_name @mesa
hostlist compute-0-0.brain.local compute-0-1.brain.local compute-0-2.brain.local
qconf -mhgrp @mesa
qconf -dhgrp @test
A queue defines the resource limits that a job may request, and on which nodes the job will be executed. In our case, we'll create a queue for each cluster sponsor, that will then be associated with the hostgroup containing their nodes.
qconf -sql
qconf -sq all.q
-
Export the all.q queue, to use as a base for the new queue
qconf -sq all.q > mesa.q
-
Edit mesa.q using an editor of your choice. In most cases, you'll only need to modify qname, hostlist, users_list, tmpdir (/scratch) and slots.
-
Load the new configuration
qconf -Aq mesa.q
qconf -mq mesa.q
qmod -d all.q
qmod -e all.q
qstat -g c
qstat -f
qstat -u '*'
The cluster has a Ganglia instance which tracks historical resource utilization on a per-node basis. Ganglia can be accessed via a browser session on the frontend node, at http://127.0.0.1/ganglia/.