EH: CS-1722: jsv_allowed_mod does not respect new binding specific switches

Author: ernst-bablick

doc/markdown/man/man1/submit.include.md

@@ -219,6 +219,10 @@ modified dynamically through the JSV interface to adapt job placement
 policy without user intervention. (see `-jsv` option below or find more
 information concerning JSV in xxqs_name_sxx_jsv(1))
 
+If a server JSV script is present, all attempts to modify binding-specific parameters using 
+`qalter` are rejected unless the *jsv_allowed_mod* parameter in the global 
+configuration (see xxqs_name_sxx_conf(5)) includes the entry *binding*.
+
 ## -binstance *instance*
 
 The -binstance switch defines the binding instance that realizes core binding on a machine.
@@ -236,6 +240,15 @@ Instances:
 * env — Binding is user-defined; the scheduler provides binding information in GCS_BINDING_CPUSET and SGE_BINDING_TOPOLOGY, but no binding is performed automatically.
 * pe — Binding is MPI-defined; binding data is written to the fourth column of the pe_hostfile as socket:core\[,socket:core...\], with numbering starting at 0 (e.g. 0:0,0:1 = cores 0 and 1 on socket 0). Depending on the MPI implementation, this additional column may be evaluated automatically to perform binding. Some MPI runtimes require additional switches, environment variables, or conversion of the socket/core format for use via runtime options or a rankfile mechanism. Consult your MPI documentation for details.
 
+All *`-b...`* switches, including `-binstance`, can be modified dynamically
+through the JSV interface to adapt job placement policy without user
+intervention. (see `-jsv` option below or find more information concerning
+JSV in xxqs_name_sxx_jsv(1)).
+
+If a server JSV script is present, all attempts to modify binding-specific parameters using
+`qalter` are rejected unless the *jsv_allowed_mod* parameter in the global
+configuration (see xxqs_name_sxx_conf(5)) includes the entry *binding*.
+
 ## -btype *binding_type*
 
 Available for `qsub`, `qrsh`, `qsh`, `qlogin`, and `qalter` only.
@@ -290,6 +303,10 @@ modified dynamically through the JSV interface to adapt job placement
 policy without user intervention. (see `-jsv` option below or find more
 information concerning JSV in xxqs_name_sxx_jsv(1))
 
+If a server JSV script is present, all attempts to modify binding-specific parameters using
+`qalter` are rejected unless the *jsv_allowed_mod* parameter in the global
+configuration (see xxqs_name_sxx_conf(5)) includes the entry *binding*.
+
 ## -bunit *binding_unit*
 
 Available for `qsub`, `qrsh`, `qsh`, `qlogin`, and `qalter` only.
@@ -380,6 +397,10 @@ through the JSV interface to adapt job placement policy without user
 intervention. (see `-jsv` option below or find more information concerning
 JSV in xxqs_name_sxx_jsv(1))
 
+If a server JSV script is present, all attempts to modify binding-specific parameters using
+`qalter` are rejected unless the *jsv_allowed_mod* parameter in the global
+configuration (see xxqs_name_sxx_conf(5)) includes the entry *binding*.
+
 ## -bfilter *filter_expression*
 
 Available for `qsub`, `qrsh`, `qsh`, `qlogin`, and `qalter` only.
@@ -422,7 +443,9 @@ through the JSV interface to adapt job placement policy without user
 intervention. (see `-jsv` option below or find more information concerning
 JSV in xxqs_name_sxx_jsv(1))
 
----
+If a server JSV script is present, all attempts to modify binding-specific parameters using
+`qalter` are rejected unless the *jsv_allowed_mod* parameter in the global
+configuration (see xxqs_name_sxx_conf(5)) includes the entry *binding*.
 
 ## -bsort *binding_sort_order*
 
@@ -510,7 +533,9 @@ through the **JSV interface** to adapt job placement policy without user
 intervention (see the `-jsv` option below or refer to
 `xxqs_name_sxx_jsv(1)` for more information).
 
----
+If a server JSV script is present, all attempts to modify binding-specific parameters using
+`qalter` are rejected unless the *jsv_allowed_mod* parameter in the global
+configuration (see xxqs_name_sxx_conf(5)) includes the entry *binding*.
 
 ## -bstart *unit*, -bstop *unit*
 
@@ -574,6 +599,10 @@ dynamically through the JSV interface to adapt job placement policy without
 user intervention. (see `-jsv` option below or find more information
 concerning JSV in xxqs_name_sxx_jsv(1))
 
+If a server JSV script is present, all attempts to modify binding-specific parameters using
+`qalter` are rejected unless the *jsv_allowed_mod* parameter in the global
+configuration (see xxqs_name_sxx_conf(5)) includes the entry *binding*.
+
 ## -binding [ *binding_instance* ] *binding_strategy*
 
 Not available anymore. Use the following options instead: `-bunit`, `-bamount`, `-btype`, `-bfilter`, `-binstance`.
@@ -582,8 +611,8 @@ Gridware Cluster Scheduler additionally provides: `-bsort`, `-bstart`, `-bstop`.
 Starting with **OCS 9.0.1** and **GCS 9.1**, CPU binding is managed directly by the scheduler.  
 Binding requests are treated as **resource requirements**; jobs start only when
 the requested topology region can be guaranteed.  
-This approach treats CPU components such as sockets, cores, threads, and memory
-units as consumable resources managed by the scheduler.
+This approach treats CPU components such as sockets, dies, cores, threads, and memory
+units (NUMA nodes and L2/L3 caches) as consumable resources managed by the scheduler.
 
 ## -b *y\[es\]* \| *n\[o\]*
 

doc/markdown/man/man5/sge_conf.md

@@ -1144,27 +1144,37 @@ limit of 60000 get requests will allow about 4000 *qstat -f* commands per second
 
 Used to define default binding behavior of jobs in the xxQS_NAMExx qmaster. Changes to the *binding_params* takes immediate effect. The following values are recognized:
 
+***default_unit*** 
+
+default is *C*. Defines the default binding unit for implicit binding requests if they are enabled via *implicit* 
+parameter.
+
+***filter***
+
+default is *NONE*. Can be set to *first_core* to disallow binding to the first core of the first socket. This reserves
+that core for other activities on compute nodes (other processes, interrupt handling, IO, ...)
+
 ***implicit***
 
 default is *false*.  Allows enabling implicit binding requests for jobs that do not have explicit binding requests.  
-For jobs with implicit request the binding amount will correspond to the amount of slots. Implicit binding unit is 
+For jobs with implicit request the binding amount will correspond to the amount of slots. Implicit binding unit is
 defined by default_unit.
 
-***default_unit*** 
-
-default is *C*. Defines the default binding unit for implicit binding requests if they are enabled via *implicit* 
-parameter.
+***mode*** 
+default is *DEFAULT*. Influences the topology reporting of the execution hosts. Possible values are: 
+*DEFAULT*, *OCS* and *GCS*. In Open Cluster Scheduler (OCS) the value for *DEFAULT* correspond with *OCS* mode. In Gridware
+Cluster Scheduler (GCS) the value for *DEFAULT* corresponds to *GCS* mode. 
+The Gridware Cluster Scheduler product allows to change the mode to *OCS* so that the products topology reporting
+remains compatible to OCS installations. In *OCS* mode memory units (NUMA nodes or CPU caches) are not reported.
+*GCS* mode is not available in Open Cluster Scheduler installations. Attempts to set the mode to *GCS* in OCS installations
+will be ignored.
+Changing this parameter requires a restart of the sge_qmaster(8) process to take effect.
 
 ***on_any_host***
 
 default is *true*. Enables scheduling of jobs with binding request to hosts that do not report topology information 
 or that do not support binding.
 
-***filter*** 
-
-default is *NONE*. Can be set to *first_core* to disallow binding to the first core of the first socket. This reserves 
-that core for other activities on compute nodes (other processes, interrupt handling, IO, ...)
-
 ## reporting_params
 
 Used to define the behavior of reporting modules in the xxQS_NAMExx qmaster. Changes to the *reporting_params* 
@@ -1389,10 +1399,15 @@ The syntax of the *jsv_url* is specified in xxqs_name_sxx_types(1).
 
 If there is a server JSV script defined with *jsv_url* parameter, then all qalter(1) modification requests for jobs are
 rejected by qmaster. With the *jsv_allowed_mod* parameter an administrator has the possibility to allow a set of 
-switches which can then be used with clients to modify certain job attributes. The value for this parameter has to be 
-a comma separated list of JSV job parameter names as they are documented in qsub(1) or the value *none* to indicate 
-that no modification should be allowed. *none* Please note that even if *none* is specified the switches 
-`-w` and `-t` are allowed for qalter.
+switches which can then be used with clients to modify certain job attributes. 
+
+The value for this parameter has to be a comma separated list of JSV job parameter names as they are documented in 
+qsub(1) or the value *none* to indicate that no modification should be allowed. Please note that even if *none* is 
+specified the switches `-w` and `-t` are allowed for qalter.
+
+Please note that for certain switches or switch combinations there are exceptions where the name that has to be 
+specified here does not correspond to the name of the switch as documented in qsub(1). Exceptions are also mentioned
+in the qsub(1) documentation.
 
 ## libjvm_path