Difference: WMSConfFile (14 vs. 15)

Line: 1 to 1

META TOPICPARENT	name="WebHome"

The WMS configuration file

Line: 24 to 24

Added:

>
>

Deleted:

<
<

LogLevel: each logging statement in the code specifies a log level. If that level is less than or equal to LogLevel the message is actually logged, otherwise it is ignored. The levels go from 1 (minimum verbosity) to 6 (maximum verbosity)

The parameters in the Common section may be overridden in the specific component sections. This usually happens with LogFile and LogLevel.

Line: 34 to 35

The attributes available in this section, in alphabetical order, are:

Added:

>
>

PropagateToLRMS (): JDL attributes to be propagated to the batch system through CREAM and BLAH $ SbRetryDifferentProtocols (false)

BrokerLib: the library implementing the brokering functionality. What is specified here is loaded with dlopen(). ("libglite_wms_helper_broker_ism.so")
CeForwardParameters: the parameters forwarded by the WM to the CE

Line: 44 to 47

DliServiceName: ??? ("data-location-interface")
EnableBulkMM: specifies if bulk matchmaking, i.e. matching multiple similar jobs in a collection in one shot, should be applied (false)
EnablePurchasingFromRgma: purchase CE information from RGMA (false)

Changed:

<
<

EnableRecovery: specifies if at startup the WM should perform a special recovery procedure for the requests that it finds already in its input. The recovery procedure is currently not reliable, so it should be disabled (false)

>
>

EnableRecovery: specifies if at startup the WM should perform a special recovery procedure for the requests that it finds already in its input. This parameter should always be set to true (false)

EnableStatusCheck: specifies if, for each request the WM reads from input, it should check the status of the request (e.g. for a submit the only acceptable status is WAITING). As for the recovery, this check is not very reliable, so it should be disabled (false)
ExpiryPeriod: the maximum time, expressed in seconds, a submitted job is kept in the overall system, from the time it arrives for the first time at the WM (86400, i.e. one day)
Input: the input source of new requests. If DispatcherType is "filelist" the source is a file; if DispatcherType is "jobdir" the source is the base dir of a JobDir structure, which is supposed to be already in place when the WM starts. A JobDir structure consists of a base dir under which lie other three subdirectories, named tmp, new, old ("${EDG_WL_TMP}/workload_manager/input.fl")

Line: 55 to 58

IsmIiPurchasingRate: the period between two ISM purchases from the BDII, in seconds (240)
IsmRgmaPurchasingRate: the period between two ISM purchases from RGMA, in seconds (120)
IsmThreads: (def=true) All the threads releated to the ISM management are taken from the thread pool (false) or created separately (false)

Changed:

<
<

IsmUpdateRate: the period between two updates of the ISM, in seconds. Note that conceptually purchasing just retrieves the list of available resources, wheres an ISM update gathers the resource information for each resource. The default value is too short (50)

>
>

IsmUpdateRate: the period between two updates of the ISM. The ISm updater is not the purchaser thread, it only checks for expired entries. The default value is too short (50)

JobWrapperTemplateDir: the job wrapper sent to the CE and then executed on Worker Node is based on a bash template which is augmented by the WM with job-specific information. This is the location where all the templates - one at the moment - are stored ("${GLITE_WMS_LOCATION}/etc/templates")
LogFile: the name of the file where messages are logged
LogLevel: each logging statement in the code specifies a log level. If that level is less than or equal to LogLevel the message is actually logged, otherwise it is ignored. The levels go from 1 (minimum verbosity) to 6 (maximum verbosity)