Message-ID: <1132822772.8823.1711700222339.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8822_359110006.1711700222338" ------=_Part_8822_359110006.1711700222338 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Below is a brief description of a few commonly used properties t= o set up the global qbwrk.conf which is distributed to workers with the com= mand
$ qbadmin w --reconfigure
Additional reading can be found at
For this example the studio will be split into hosts based on their role= i.e.:
Use the below examples to model templates of your studio layout
Warning template name [default]
is reserved for assignment =
to all nodes
[Farm]
proxy_execution_mode =3D user
worker_properties =3D host.nuke6.2=3D1, host.maya2011=3D1
<=
br />worker_cpus =3D 1
worker_groups =3D all,linux=
,maya,nuke
Above is an example of a template that can be set using logical na=
mes to assign a set of commonly used properties
"[Farm]
" is the name of the template that can be =
used to assign the following properties. you can set as many of these as yo=
u see fit
"proxy_execution_mode
" is property to set how Qub=
e! executes in your environment "User" means the submitting user'=
s network credentials and permissions will be used
*additional readin=
g
"worker_properties
" is for assigning global resou=
rces such as licenses global resources are set in qb.conf
*additional=
reading
"worker_cpus
" is a property to hard set the amoun=
t of cpu's on the worker *if left commented worker default cpu's are calcul=
ated*
"worker_groups
" one or multiple groups the worker=
belongs to
Below is an exapmle of how to assign the above template to a list of wor= ker hosts
[render2d01]: Farm #[render3d[01-05]]: Farm
[wo=
rstation01]: Farm
worker_description =3D "lead TD wo=
rkstation"
Above is an example of how to assign the template [Farm]
"[render2d01]: Farm
" is setting the template to a=
single machine
"[render3d[01-05]]: Farm
" is setting the template=
to a range of machines
"[worstation01]: Farm
" is setting the template to=
worstation01
"worker_description =3D
" assigns a description to=
the above worker as an additional property
using the below example you can assign properties by OS
[default]
will assign to all OS's
[osx]
worker_description =3D "All OS X wor=
kers"
[linux]
worker_description =3D "All Linux w=
orkers"
[winnt]
worker_description =3D "All Window=
s workers"
Use the below example to assign clusters to your workers note the exampl=
es of submitting jobs from the cmd line.
Clusters can also be assigne=
d using the template method above
additional reading :
Copy below and alter for your environment
[render3d01]
worker_cluster =3D "/farm"=
;
worker_restrictions =3D "/farm or /farm/*"
above is to define a host that will run jobs in any cluster at /fa=
rm or 1 level below - done with the '*'
Copy below and alter for your environment
[render2d01]
worker_cluster =3D "/farm/nuke=
"
worker_restrictions =3D "/farm/nuke or /farm/=
nuke/+"
above is to define a host that will only run jobs in /farm/nuke or=
any level below - done with the '+'
Copy below and alter for your environment
[workstation05]
worker_cluster =3D "/farm/n=
uke/workstations"
worker_restrictions =3D "/far=
m/nuke/workstations"
above is to define a host that will only run jobs in /farm/nuke/workstat= ions
submit a job that will run only in /farm:
"qbsub -cluster /farm -restriction /farm"
submit a job that will prefer to run in /farm/nuke, but could run in any= host in /farm or in the first level below /farm
"qbsub -cluster /farm/nuke -restriction '/farm or /farm/*'&qu=
ot;
submit a job that will prefer to run in /farm/nuke/workstations, but&nbs= p;could run in any host at any level at /farm or below
"qbsub -cluster /farm/nuke/workstations -restriction '/farm o=
r /farm/+' hostname"