Configuration files and attributes

Configuration of the Command line User Interface is accomplished through the files:

$GLITE_LOCATION/etc/<vo name>/glite_wmsui.conf

for the VO specific configuration. Description of this file can be found at UI VO specific configuration, and

$GLITE_LOCATION/etc/glite_wmsui_cmd_var.conf

(Note: if the variable GLITE_WMS_LOCATION is set, all the configuration files will be searched starting from this location)

Update the content of the latter file according to your needs as explained hereafter.

The glite_wmsui_cmd_var.conf file is a classad containing the following fields:

  • requirements
this is an expression representing the default value for the requirements expression in the JDL job description. This parameter is mandatory. The value of this parameter is assigned by the UI to the requirements attribute in the JDL if not specified by the user. If the user has instead provided an expression for the requirements attribute in the JDL, the one specified in the configuration file is added (in AND) to the existing one.

E.g. if in the glite_wmsui_cmd_var.conf configuration file there is:

	requirements = other.GlueCEStateStatus == "Production" ;

and in the JDL file the user has specified:

	requirements = other.GlueCEInfoLRMSType == "PBS";

then the job description that is passed to the WMS contains

	requirements = (other.GlueCEInfoLRMSType == "PBS") && (other.GlueCEStateStatus == "Production");

Obviously the setting TRUE for the requirements in the configuration file does not have any impact on the evaluation of job requirements as it would result in:

	requirements = (other.GlueCEInfoLRMSType == "PBS") && TRUE ;

  • rank
this is an expression representing the default value for the rank expression in the JDL job description. The value of this parameter is assigned by the UI to the rank attribute in the JDL if not specified by the user. This parameter is mandatory.

  • RetryCount
this is an integer representing the default value for the number of submission retries for a job upon failure due to some grid component (i.e. not to the job itself). The value of this parameter is assigned by the UI to the RetryCount attribute in the JDL if not specified by the user.

  • DefaultVo
this is a string representing the name of the virtual organisation to be taken as the user VO (VirtualOrganisation attribute in he JDL) if not specified by the user neither in the credentials VOMS extension, nor directly in the job description nor through the --vo option. This attribute can be either set to unspecified or not included at all in the file to mean that no default is set for the VO.

  • ErrorStorage
this is a string representing the path of the directory where the UI creates log files. This directory is not created by the UI, so It has to be an already existing directory. Default for this parameter is /tmp.

  • OutputStorage
this is a string defining the path of the directory where the job OutputSandbox files are stored if not specified by the user through commands options. This directory is not created by the UI, so It has to be an already existing directory. Default for this parameter is /tmp.

  • ListenerStorage
this is a string defining the path of the directory where are created the pipes where the glite_wms_console_shadow process saves the job standard streams for interactive jobs. Default for this parameter is /tmp.

  • LoggingTimeout
this is an integer representing the timeout in seconds for asynchronous logging function called by the UI when logging events to the LB. Recommended value for UI that are non-local to the logging service (glite-lb-logd logging daemon) is not less than 30 seconds.

  • LoggingSyncTimeout
this is an integer representing the timeout in seconds for synchronous logging function called by the UI when logging events to the LB. Recommended value is not less than 30 seconds.

  • DefaulStatusLevel
this is an integer defining the default level of verbosity for the glite-job-status command. Possible values are 0,1,2 and 3. 0 means minimum verbosity. Default for this parameter is 1.

  • DefaultLogInfoLevel
this is an integer defining the default level of verbosity for the glite-job-logging-info command. Possible values are 0,1,2 and 3. 0 means minimum verbosity. Default for this parameter is 1.

  • NSLoggerLevel
this is an integer defining the quantity of information logged by the NS client. Possible values range from 0 to 6. 0 is the defaults and means that no information is logged. Default for this parameter is 0.

Hereafter is provided an example of the $GLITE_LOCATION/etc/glite_wmsui_cmd_var.conf configuration file:

[
 requirements = other.GlueCEStateStatus == "Production" ;
 rank = - other.GlueCEStateEstimatedResponseTime ;
 RetryCount = 3 ;
 ErrorStorage= "/var/tmp" ;
 OutputStorage="/tmp";
 ListenerStorage = "/tmp"
 LoggingTimeout = 30 ;
 LoggingSyncTimeout = 45 ;
 DefaultStatusLevel = 1 ;
 DefaultLogInfoLevel = 0;
 NSLoggerLevel = 2;
 DefaultVo = "cms";
]

The files:

$GLITE_LOCATION/etc/glite_wmsui_cmd_err.conf

and

$GLITE_LOCATION/etc/glite_wmsui_cmd_help.conf

contain respectively the error codes and error messages returned by the UI and the text describing the commands usage.

Environment Variables

  • GLITE_WMSUI_CONFIG_VAR
Non-standard location of the command line interface configuration file glite_wmsui_cmd_var.conf. This variable points to the file absolute path

  • GLITE_WMSUI_CONFIG_VO
Non-standard location of the vo-specific GUI configuration file glite_wmsui.conf. This variable points to the file absolute path.

  • EDG_WL_LOG_DESTINATION
Non-standard address of the the LB logging service (glite-lb-locallogger logging daemon) in the format <host FQDN>[:<port>] . If not set the LB logging service running on the WMS node is targeted for logging job information.

What is Grid

The Grid is an emerging infrastructure that will fundamentally change the way we think about - and use - computing. The basic idea is very simple, since it is about harnessing unused resources through the Internet, or a corporate Intranet, to solve major computational problems that require far more computing power and data storage than that available at any single location

EGEE Project

The Enabling Grids for E-sciencE (EGEE) project is funded by the European Commission and aims to build on recent advances in grid technology and develop a service grid infrastructure


EGEE Home Page