There are several way to control which hosts the supervisor will select when deciding where to start job instances on the farm.
- Hosts: Send only to an explicit set of workers
- Host Groups: Send only to an explicit pre-defined group of workers
- Host Order: Select hosts in a certain preferential order
| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
Qube! allows users to specify a list of hosts, for the job to run on. This is a comma-delimited list of hostnames.
Example
% qbsub --hosts "qb001,qb002" command
Omit Hosts
Qube! allows users to specify a list of hosts on which the job is restricted from running. This is a comma-delimited list of hostnames. This blacklists the hosts from running on these hosts.
Example
% qbsub --omithosts "qb001,qb002" command
| Anchor | ||||
|---|---|---|---|---|
|
Qube! allows the administrator to organize the farm into clusters or host groups. These groups have no hierarchy, and hosts are allowed membership in multiple groups. In order to restrict a job to a specific set of hosts, the user may specify in the 'group' field of the job, which groups they want the job restricted to.
Example
% qbsub --groups "vfx,character" Render my/file.ma
| Anchor | ||||
|---|---|---|---|---|
|
This is the opposite of the Host Groups option, where the job will restrict itself from running upon any hosts which are contained by the specified groups.
Example
% qbsub --omitgroups "vfx,character" command
| Anchor | ||||
|---|---|---|---|---|
|
...