HOST_CONF(5)               Grid Engine File Formats               HOST_CONF(5)



[1mNAME[0m
       host_conf - Grid Engine execution host configuration file format

[1mDESCRIPTION[0m
       [4mHost_conf[24m  reflects  the  format of the template file for the execution
       host configuration.  Via the [1m-ae [22mand [1m-me [22moptions of the  [4mqconf[24m(1)  com-
       mand,  you  can add execution hosts and modify the configuration of any
       execution host in the cluster. Default execution host entries are added
       automatically  as  soon as a [4mge_execd[24m(8) registers to [4mge_qmaster[24m(8) for
       the very first time from a certain host. The [4mqconf[24m(1) [1m-sel  [22mswitch  can
       be  used to display a list of execution host being currently configured
       in your Grid Engine system. Via the [1m-se [22moption you can print the execu-
       tion host configuration of a specified host.

       The  special  hostname  "global"  can  be used to define cluster global
       characteristics.

       Note, Grid Engine allows backslashes (\)  be  used  to  escape  newline
       (\newline)  characters. The backslash and the newline are replaced with
       a space (" ") character before any interpretation.

[1mFORMAT[0m
       The format of a [4mhost_conf[24m file is defined as follows:

   [1mhostname[0m
       The execution hosts name as defined for [4mhost_name[24m in [4msge_types[24m(1).

   [1mload_scaling[0m
       A comma separated list of scaling values to be applied to each or  part
       of  the  load  values being reported by the [4mge_execd[24m(8) on the host and
       being defined in the cluster global "host"  complex  (see  [4mcomplex[24m(5)).
       The  load  scaling  factors are intended to level hardware or operating
       system specific differences between execution hosts.

       The syntax of a load factor specification is as follows: First the name
       of the load value (as defined in the "host" complex) is given and, sep-
       arated by an equal sign, the load scaling value is provided. No  blanks
       are allowed in between the load_scaling value string.

       The  parameter [1mload_scaling [22mis not meaningful for the definition of the
       "global" host.

   [1mcomplex_values[0m
       [1mcomplex_values [22mdefines quotas for resource attributes managed via  this
       host.  Each  complex attribute is followed by an "=" sign and the value
       specification compliant with  the  complex  attribute  type  (see  [4mcom-[0m
       [4mplex[24m(5)).  Quota specifications are separated by commas.

       The  quotas  are  related  to the resource consumption of all jobs on a
       host in the case of consumable resources (see [4mcomplex[24m(5) for details on
       consumable  resources)  or they are interpreted on a per job slot basis
       in the case of non-consumable resources. Consumable resource attributes
       are  commonly  used to manage free memory, free disk space or available
       floating software  licenses  while  non-consumable  attributes  usually
       define distinctive characteristics like type of hardware installed.

       For  consumable  resource  attributes  an  available resource amount is
       determined by subtracting the current resource consumption of all  run-
       ning  jobs  on the host from the quota in the [1mcomplex_values [22mlist. Jobs
       can only be dispatched to a host if no  resource  requests  exceed  any
       corresponding  resource availability obtained by this scheme. The quota
       definition in the [1mcomplex_values [22mlist is automatically replaced by  the
       current  load  value  reported for this attribute, if load is monitored
       for this resource and if the reported load value is more stringent than
       the quota. This effectively avoids oversubscription of resources.

       [1mNote:  [22mLoad  values  replacing the quota specifications may have become
       more stringent because they have been scaled (see  [1mload_scaling  [22mabove)
       and/or  load  adjusted  (see [4msched_conf[24m(5)).  The [4m-F[24m option of [4mqstat[24m(1)
       and the load display in the [4mqmon[24m(1) queue control dialog (activated  by
       clicking  on  a  queue  icon  while the "Shift" key is pressed) provide
       detailed information on the actual availability of consumable resources
       and on the origin of the values taken into account currently.

       [1mNote  also:  [22mThe  resource  consumption  of  running jobs (used for the
       availability calculation) as well as the resource requests of the  jobs
       waiting  to  be  dispatched  either  may  be derived from explicit user
       requests during job submission (see the [4m-l[24m option to [4mqsub[24m(1)) or from a
       "default"  value  configured for an attribute by the administrator (see
       [4mcomplex[24m(5)).  The [4m-r[24m option to [4mqstat[24m(1) can be used for retrieving full
       detail on the actual resource requests of all jobs in the system.

       For  non-consumable  resources  Grid  Engine  simply compares the job's
       attribute requests with the corresponding specification in [1mcomplex_val-[0m
       [1mues  [22mtaking  the  relation operator of the complex attribute definition
       into account (see [4mcomplex[24m(5)).  If the  result  of  the  comparison  is
       "true", the host is suitable for the job with respect to the particular
       attribute. For parallel jobs each job slot to be occupied by a parallel
       task is meant to provide the same resource attribute value.

       [1mNote:  [22mOnly  numeric  complex  attributes  can be defined as consumable
       resources and hence non-numeric attributes are always handled on a  per
       job slot basis.

       The  default  value  for  this parameter is NONE, i.e. no administrator
       defined resource attribute quotas are associated with the host.

   [1mload_values[0m
       This entry cannot be configured but is only  displayed  in  case  of  a
       [4mqconf[24m(1)  [1m-se [22mcommand. All load values are displayed as reported by the
       [4mge_execd[24m(8) on the host. The load values are enlisted in a comma  sepa-
       rated  list.  Each load value start with its name, followed by an equal
       sign and the reported value.

   [1mprocessors[0m
       [1mNote: [22mDeprecated, may be removed in future release.
       This entry cannot be configured but is only  displayed  in  case  of  a
       [4mqconf[24m(1)  [1m-se  [22mcommand. Its value is the number of processors which has
       been detected by [4mge_execd[24m(8) on the corresponding host.

   [1musage_scaling[0m
       The format is equivalent to [1mload_scaling [22m(see above),  the  only  valid
       attributes  to  be scaled however are [1mcpu [22mfor CPU time consumption, [1mmem[0m
       for Memory consumption aggregated over the life-time of jobs and [1mio [22mfor
       data  transferred via any I/O devices. The default NONE means "no scal-
       ing", i.e. all scaling factors are 1.

   [1muser_lists[0m
       The [1muser_lists [22mparameter contains a comma separated list of  so  called
       user  access lists as described in [4maccess_list[24m(5).  Each user contained
       in at least one of the enlisted access lists has access to the host. If
       the  [1muser_lists  [22mparameter  is  set  to NONE (the default) any user has
       access being not explicitly  excluded  via  the  [1mxuser_lists  [22mparameter
       described  below.   If  a  user  is  contained  both  in an access list
       enlisted in [1mxuser_lists [22mand [1muser_lists [22mthe user is denied access to the
       host.

   [1mxuser_lists[0m
       The  [1mxuser_lists [22mparameter contains a comma separated list of so called
       user access lists as described in [4maccess_list[24m(5).  Each user  contained
       in  at  least one of the enlisted access lists is not allowed to access
       the host. If the [1mxuser_lists [22mparameter is set to NONE (the default) any
       user  has  access.   If  a  user  is  contained  both in an access list
       enlisted in [1mxuser_lists [22mand [1muser_lists [22mthe user is denied access to the
       host.

   [1mprojects[0m
       The [1mprojects [22mparameter contains a comma separated list of projects that
       have access to the host. Any projects  not  in  this  list  are  denied
       access  to  the  host.  If  set  to NONE (the default), any project has
       access that is not specifically excluded via  the  [1mxprojects  [22mparameter
       described  below.  If  a  project is in both the [1mprojects [22mand [1mxprojects[0m
       parameters, the project is denied access to the host.

   [1mxprojects[0m
       The [1mxprojects [22mparameter contains a comma  separated  list  of  projects
       that  are  denied  access to the host. If set to NONE (the default), no
       projects are denied access other than those denied access based on  the
       [1mprojects  [22mparameter  described  above.   If  a  project  is in both the
       [1mprojects [22mand [1mxprojects [22mparameters, the project is denied access to  the
       host.

   [1mreport_variables[0m
       The [1mreport_variables [22mparameter contains a comma separated list of vari-
       ables that shall be written  to  the  reporting  file.   The  variables
       listed  here  will  be written to the reporting file when a load report
       arrives from an execution host.

       Default settings can be done in the global host. Host specific settings
       for report_variables will override settings from the global host.

[1mSEE ALSO[0m
       [4mge_intro[24m(1),  [4mge_types[24m(1),  [4mqconf[24m(1),  [4muptime[24m(1),  [4maccess_list[24m(5), [4mcom-[0m
       [4mplex[24m(5), [4mge_execd[24m(8), [4mge_qmaster[24m(8).

[1mCOPYRIGHT[0m
       See [4mge_intro[24m(1) for a full statement of rights and permissions.



GE 6.2u2                 $Date: 2008/07/08 09:10:05 $             HOST_CONF(5)
