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



NNAAMMEE
       host_conf - Grid Engine execution host configuration file format

DDEESSCCRRIIPPTTIIOONN
       _H_o_s_t___c_o_n_f  reflects  the  format of the template file for the execution
       host configuration.  Via the --aaee and --mmee options of the  _q_c_o_n_f(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 _s_g_e___e_x_e_c_d(8) registers to _s_g_e___q_m_a_s_t_e_r(8) for
       the very first time from a certain host. The _q_c_o_n_f(1) --sseell  switch  can
       be  used  to  display  a list of execution host currently configured in
       your Grid Engine system. Via the --ssee option you can print the execution
       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.

FFOORRMMAATT
       The format of a _h_o_s_t___c_o_n_f file is defined as follows:

   hhoossttnnaammee
       The execution hosts name as defined for _h_o_s_t___n_a_m_e in _s_g_e___t_y_p_e_s(1).

   llooaadd__ssccaalliinngg
       A comma separated list of scaling values to be applied to each or  part
       of the load values reported by the _s_g_e___e_x_e_c_d(8) on the host and defined
       in the cluster global "host" complex (see _c_o_m_p_l_e_x(5)).  The load  scal-
       ing  factors  are intended to balance hardware or operating system spe-
       cific 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 llooaadd__ssccaalliinngg is not meaningful for the definition of the
       "global" host.

   ccoommpplleexx__vvaalluueess
       ccoommpplleexx__vvaalluueess defines 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  _c_o_m_-
       _p_l_e_x(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 _c_o_m_p_l_e_x(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 ccoommpplleexx__vvaalluueess list. 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 ccoommpplleexx__vvaalluueess list 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.

       NNoottee::  Load  values  replacing the quota specifications may have become
       more stringent because they have been scaled (see  llooaadd__ssccaalliinngg  above)
       and/or  load  adjusted  (see _s_c_h_e_d___c_o_n_f(5)).  The _-_F option of _q_s_t_a_t(1)
       and the load display in the _q_m_o_n(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.

       NNoottee  aallssoo::  The  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 _-_l option to _q_s_u_b(1)) or from a
       "default"  value  configured for an attribute by the administrator (see
       _c_o_m_p_l_e_x(5)).  The _-_r option to _q_s_t_a_t(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 ccoommpplleexx__vvaall--
       uueess  taking  the  relation operator of the complex attribute definition
       into account (see _c_o_m_p_l_e_x(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.

       NNoottee::  Only  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.

   llooaadd__vvaalluueess
       This entry cannot be configured but is only  displayed  in  case  of  a
       _q_c_o_n_f(1)  --ssee command. All load values are displayed as reported by the
       _s_g_e___e_x_e_c_d(8) on the host. The load values are listed in a  comma  sepa-
       rated  list.  Each load value start with its name, followed by an equal
       sign and the reported value.

   pprroocceessssoorrss
       This entry cannot be configured but is only  displayed  in  case  of  a
       _q_c_o_n_f(1)  --ssee  command. Its value is the number of processors which has
       been detected by _s_g_e___e_x_e_c_d(8) on the corresponding host.

   uussaaggee__ssccaalliinngg
       The format is equivalent to llooaadd__ssccaalliinngg (see above),  the  only  valid
       attributes  to  be scaled however are ccppuu for CPU time consumption, mmeemm
       for Memory consumption aggregated over the life-time of jobs and iioo for
       data  transferred via any I/O devices. The default NONE means "no scal-
       ing", i.e. all scaling factors are 1.

   uusseerr__lliissttss
       The uusseerr__lliissttss parameter contains a comma separated list of user access
       lists  as described in _a_c_c_e_s_s___l_i_s_t(5).  Each user contained in at least
       one of the  listed  access  lists  has  access  to  the  host.  If  the
       uusseerr__lliissttss  parameter  is set to NONE (the default) any user has access
       not explicitly excluded via the xxuusseerr__lliissttss parameter described  below.
       If a user is contained both in an access list listed in xxuusseerr__lliissttss and
       uusseerr__lliissttss the user is denied access to the host.

   xxuusseerr__lliissttss
       The xxuusseerr__lliissttss parameter contains  a  comma  separated  list  of  user
       access lists as described in _a_c_c_e_s_s___l_i_s_t(5).  Each user contained in at
       least one of the listed access lists is not allowed to access the host.
       If  the xxuusseerr__lliissttss parameter is set to NONE (the default) any user has
       access.  If a user is contained  both  in  an  access  list  listed  in
       xxuusseerr__lliissttss and uusseerr__lliissttss the user is denied access to the host.

   pprroojjeeccttss
       The pprroojjeeccttss parameter 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  xxpprroojjeeccttss  parameter
       described  below.  If  a  project is in both the pprroojjeeccttss and xxpprroojjeeccttss
       parameters, the project is denied access to the host.

   xxpprroojjeeccttss
       The xxpprroojjeeccttss parameter 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
       pprroojjeeccttss  parameter  described  above.   If  a  project  is in both the
       pprroojjeeccttss and xxpprroojjeeccttss parameters, the project is denied access to  the
       host.

   rreeppoorrtt__vvaarriiaabblleess
       The rreeppoorrtt__vvaarriiaabblleess parameter 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.

SSEEEE AALLSSOO
       _s_g_e___i_n_t_r_o(1),  _s_g_e___t_y_p_e_s(1),  _q_c_o_n_f(1), _u_p_t_i_m_e(1), _a_c_c_e_s_s___l_i_s_t(5), _c_o_m_-
       _p_l_e_x(5), _s_g_e___e_x_e_c_d(8), _s_g_e___q_m_a_s_t_e_r(8).

CCOOPPYYRRIIGGHHTT
       See _s_g_e___i_n_t_r_o(1) for a full statement of rights and permissions.



GE 6.1                   $Date: 2007/07/19 08:17:17 $             HOST_CONF(5)
