YAIM configuration variables

site-info.def configuration variables

The following tables contain a list of variables used to configure most of the yaim modules. General variables can be found in:

• /opt/glite/yaim/examples/siteinfo/site-info.def : general variables that need a value specific to the site and that must be configured by the site admin.
• /opt/glite/yaim/defaults/site-info.pre : general variables that have a meaningful default value and do not need to be changed unless the site admin is interested in a more advanced configuration.
• /opt/glite/yaim/defaults/site-info.post : the same as site-info.pre but sourced after the two previous files. These allows to define variables whose default value depend on variables like INSTALL_ROOT.

In order to know whether a variable is compulsory in the configuration of a node type or not, please check the relevant node type section in this page, where you can find a description of which set of variables is actually needed for each node type.

NOTE: The following distribution in site-info.def, site-info.pre and site-info.post is available for yaim core >= 4.0.5-1. In lower versions the distribution may be different (most of the variables were distributed in site-info.def) but the meaning of the variables is the same and you can still search for variables in this document for any version of yaim core.

site-info.def

Variable name	Description	Example	YAIM version >=
APEL_DB_PASSWORD	Database password for APEL	APEL_DB_PASSWORD=mypassword	3.0.1-0
ARGUS_PEPD_ENDPOINTS	Required when the ARGUS PEP client is to be configured. It is the PEP Server endpoint URL which the ARGUS client should use.	ARGUS_PEPD_ENDPOINTS="https://pepd.example.org:8154/authz"	4.0.12-1
BATCH_LOG_DIR	Batch system log directory. for Torque/PBS, this must be set to the directory containing the server_logs directory; usually /var/torque	BATCH_LOG_DIR=/var/spool/pbs	4.0.0-12
BATCH_SERVER	Batch server hostname	BATCH_SERVER=yaim-pbs.cern.ch	3.1.1-1
BATCH_SPOOL_DIR	Your batch system's log directory. It will replaced by BATCH_LOG_DIR in glite-yaim-core >= 4.0.0-12.	deprecated	deleted glite-yaim-core >= 4.0.0-12
BATCH_VERSION	The version of the Local Resource Managment System	BATCH_VERSION=torque-2.3.0	3.0.1-0
BDII_DELETE_DELAY	The cache period for LDAP records that disappeared from the BDII's input; by default it should be zero, but due to a bug affecting some versions of EMI-1 node types, the admin may need to define it explicitly	BDII_DELETE_DELAY=0
BDII_HOST	BDII hostname	BDII_HOST=yaim-bdii.cern.ch	3.0.1-0
BDII_LIST	Optional variable to define a list of top level BDIIs to support the automatic failover in the GFAL clients and information system tools. The syntax is my-bdii1.$MY_DOMAIN:port1[,my-bdii22.$MY_DOMAIN:port2[...]]. A list of BDIIs is supported by GFAL, lcg_util, lcg-info, lcg-infosites, lcg-ManageVOTag, lcg-tags and glite-sd-query.	BDII_LIST="yaim-bdii.cern.ch:2170,other-bdii.cern.ch:2170"	4.0.5-1
CE_BATCH_SYS	Batch system used by the CE. Possible values are 'torque'', 'lsf', 'pbs', 'condor' and 'sge'	CE_BATCH_SYS=torque	3.0.1-0
CE_CAPABILITY	This YAIM variable is a blank separated list and is used to set the GlueCECapability attribute where: 1) CPUScalingReferenceSI00=<referenceCPU-SI00>: this is the reference CPU SI00 that has to be calculated in two possible ways: a) If the batch system scales the published CPU time limit (GlueCEPolicyMaxCPUTime) to a reference CPU power then CPUScalingReferenceSI00 should be the SI00 rating for that reference; b) If the batch system does not scale the time limit then CPUScalingReferenceSI00 should be the SI00 rating of the least powerful core in the cluster. Sites which have moved to the HEP-SPEC benchmark should use it but converted to SI00 units using the scaling factor of 250, i.e. SI00 = 250*HEP-SPEC. 2) Share=<vo-name>:<vo-share>: this value is used to express VO fairshares targets. If there is no special share, this value MUST NOT be published. <vo-share> can assume values between 1 and 100 (it represents a percentage). Please note that the sum of the shares over all WLCG VOs MUST BE less than or equal to 100. If the worker nodes behind the CE provide the glexec facility (for WLCG VOs), an extra capability glexec must be added to the list. For lcg-CE >= 3.1.42 this variable may be set in /opt/glite/yaim/examples/siteinfo/services/lcg-ce instead of in site-info.def	CE_CAPABILITY="CPUScalingReferenceSI00=100 Share=dteam:20 Share=atlas:10 glexec"	4.0.7-1
CE_CPU_MODEL	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostProcessorModel attribute. System administrators MUST set this variable to the name of the processor model as defined by the vendor for the Worker Nodes in a SubCluster. Given the fact that SubClusters can be heterogeneous, this refers to the typical processor model for the nodes of a SubCluster.	CE_CPU_MODEL=Xeon	3.0.1-0
CE_CPU_SPEED	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostProcessorClockSpeed attribute. System administrators MUST set this variable to the name of the processor clock speed expressed in MHz for the Worker Nodes in a SubCluster. Given the fact that SubClusters can be heterogeneous, this refers to the typiceal processor for the nodes of a SubCluster. If you need to publish this value correctly, you are requested to split your CE/Subclusters to be homogenous.	CE_CPU_SPEED=2334	3.0.1-0
CE_CPU_VENDOR	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostProcessorVendor attribute. System administrators MUST set this variable to the name of the processor vendor for the Worker Nodes in a SubCluster. Given the fact that SubClusters can be heterogeneous, this refers to the typical processor for the nodes of a SubCluster.	CE_CPU_VENDOR=intel	3.0.1-0
CE_HOST	Computing Element Hostname	CE_HOST=yaim-ce.cern.ch	3.0.1-0
CE_DATADIR	This YAIM variable is used to set the GlueCEInfoDataDir attribute. This is an optional variable that can be left undefined. Otherwise, system administrators should set it to the path of a shared directory available for application data. Typically a POSIX accessible transient disk space shared between the Worker Nodes. It may be used by MPI applications or to store intermediate files that need further processing by local jobs or as staging area, specially if the Worker Node have no internet connectivity.	CE_DATADIR=/mypath	3.0.1-0
CE_INBOUNDIP	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostNetworkAdapterInboundIP attribute. System administrators MUST set this variable to either FALSE or TRUE (in uppercase !) to express the permission for inbound connectivity for the WNs in the SubCluster, even if limited.	CE_INBOUNDIP=FALSE	3.0.1-0
CE_LOGCPU	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueSubClusterLogicalCPUs. System administrators MUST set this variable to the value of the “Total number of cores/hyperthreaded CPUs in the SubCluster, including the nodes part of the SubCluster that are temporary down or offline”. In order to overcome the current YAIM limitation when a new CE head node giving access to the same batch resources is added to a site, site admins MUST set the CE_LOGCPU YAIM variable to 0 if the resources used by the new subclusters are already published via another CE.	CE_LOGCPU=1472	4.0.3-9
CE_MINPHYSMEM	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostMainMemoryRAMSize attribute. System administrators MUST set this variable to the Total physical memory of a WN in the SubCluster expressed in MegaBytes. Given the fact that SubClusters can be heterogeneous, this refers to the typical worker node in a SubCluster. It is advisable to publish here the minimum total physical memory of the WNs in the SubCluster expressed in MegaBytes. If you need to publish this value correctly, you are requested to split your CE/Subclusters to be homogenous.	CE_MINPHYSMEM=16000	3.0.1-0
CE_MINVIRTMEM	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostMainMemoryVirtualSize attribute. System administrators MUST set this variable to the Total virtual memory of a WN in the SubCluster expressed in MegaBytes. Given the fact that SubClusters can be heterogeneous, this refers to the typical worker node in a SubCluster. It is advisable to publish here the minimum total virtual memory of the WNs in the SubCluster expressed in MegaBytes. If you need to publish this value correctly, you are requested to split your CE/Subclusters to be homogenous.	CE_MINVIRTMEM=32000	3.0.1-0
CE_OS	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostOperatingSystemName attribute. System administrators MUST set this variable to the name of the operating system used on the Worker Nodes part of the SubCluster. - see https://wiki.egi.eu/wiki/Operations/HOWTO05	CE_OS="ScientificSL"	3.0.1-0
CE_OS_RELEASE	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostOperatingSystemRelease attribute. System administrators MUST set this variable to the release of the operating system used on the Worker Nodes part of the SubCluster - see https://wiki.egi.eu/wiki/Operations/HOWTO05	CE_OS_RELEASE=6.3	3.0.1-0
CE_OS_VERSION	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostOperatingSystemVersion attribute. System administrators MUST set this variable to the version of the operating system used on the Worker Nodes part of the SubCluster - see https://wiki.egi.eu/wiki/Operations/HOWTO05	CE_OS_VERSION=Carbon	3.0.1-0
CE_OS_ARCH	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostArchitecturePlatformType attribute. System administrators MUST set this variable to the Platform Type of the WN in the SubCluster. Given the fact that SubClusters can be heterogeneous, this refers to the typical worker node in a SubCluster. More information can be found here: https://wiki.egi.eu/wiki/Operations/HOWTO06	CE_OS_ARCH=i686	3.0.1-0
CE_OTHERDESCR	This YAIM variable is used to set the GlueHostProcessorOtherDescription attribute. The value of this variable MUST be set to: Cores=<typical-number-of-cores-per-CPU>[,Benchmark=<your-value>-HEP-SPEC06] where <typical-number-of-cores-per-CPU> is equal to the number of cores per CPU of a typical Worker Node in a SubCluster. The second value of this attribute MUST be published only in the case the CPU power of the SubCluster is computed using the Benchmark HEP-SPEC06. The syntax is Cores=value[,Benchmark=value-HEP-SPEC06].	CE_OTHERDESCR="Cores=4,Benchmark=100-HEP-SPEC06"	4.0.7-1
CE_OUTBOUNDIP	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostNetworkAdapterOutboundIP attribute. System administrators MUST set this variable to either FALSE or TRUE (in uppercase !) to express the permission for direct outbound connectivity for the WNs in the SubCluster, even if limited.	CE_OUTBOUNDIP=FALSE	3.0.1-0
CE_PHYSCPU	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueSubClusterPhysicalCPUs. System administrators MUST set this variable to the value of the “Total number of real CPUs/physical chips in the SubCluster, including the nodes part of the SubCluster that are temporarily down or offline”. In order to overcome the current YAIM limitation when a new CE head node giving access to the same batch resources is added to a site, site admins MUST set the CE_PHYSCPU YAIM variable to 0 if the resources used by the new subclusters are already published via another CE.	CE_PHYSCPU=736	4.0.3-9
CE_RUNTIMEENV	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostApplicationSoftwareRunTimeEnvironment. It should define a space separated list of software tags supported by the site. The list can include VO-specific software tags. In order to ensure backwards compatibility it should include the entry 'LCG-2', the current middleware version and the list of previous middleware tags	CE_RUNTIMEENV="LCG-2 LCG-2_1_0 LCG-2_1_1 LCG-2_2_0 LCG-2_3_0 LCG-2_3_1 LCG-2_4_0 LCG-2_5_0 LCG-2_6_0 LCG-2_7_0 GLITE-3_0_0 GLITE-3_1_0 R-GMA"	3.0.1-0
CE_SF00	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostBenchmarkSF00 attribute. It's the performance index of your fabric in SpecFloat 2000. For some examples of Spec values see http://www.specbench.org/osg/cpu2000/results/cint2000.html	CE_SF00=0	3.0.1-0
CE_SI00	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostBenchmarkSI00 attribute. It's the performance index of your fabric in SpecInt 2000. System administrators MUST set this variable as indicated in page 5 of https://twiki.cern.ch/twiki/pub/LCG/WLCGCommonComputingReadinessChallenges/WLCG_GlueSchemaUsage-1.8.pdf. For some examples of Spec values see http://www.specbench.org/osg/cpu2000/results/cint2000.html	CE_SI00=381	3.0.1-0
CE_SMPSIZE	Needed for cream CE and lcg-CE in non-cluster mode: This YAIM variable is used to set the GlueHostArchitectureSMPSize attribute. System administrators MUST set this variable to the number of Logical CPUs (cores) of the WN in the SubCluster. Given the fact that SubClusters can be heterogeneous, this refers to the typical worker node in a SubCluster. If you need to publish this value correctly, you are requested to split your CE/Subclusters to be homogenous.	CE_SMPSIZE=2	3.0.1-0
CLASSIC_STORAGE_DIR	The root storage directory on CLASSIC_HOST. This variable is no longer used after introducing SE_MOUNT_INFO_LIST. See bug 33210 for lcg CE and bug 46681 for cream CE to check in which yaim module version the SE_MOUNT_INFO_LIST was used so you can deprecate this variable.	deprecated	3.0.1-0
CREAM_PEPC_RESOURCEID	If specified and configuration of ARGUS PEP client is enabled then yaim will configure ARGUS on the cream CE, otherwise ARGUS setup is skipped on that node. The variable specifies the ARGUS resource ID to be used.	CREAM_PEPC_RESOURCEID=urn:mysitename.org:resource:ce	4.0.12-1
DPM_HOST	Host name of the DPM host	DPM_HOST=yaim.dpm.cern.ch	3.0.1-0
FTS_HOST	FTS server hostname. It's deprecated. See the FTS section of this twiki to know which variables are needed to configure a FTS.	deprecated	3.0.1-0
FTS_SERVER_URL	The URL of the File Transfer Service server	FTS_SERVER_URL="https://yaim-fts.cern.ch:8443/path/glite-data-transfer-fts"	3.0.1-0
GENERAL_PEPC_RESOURCEID	If specified and configuration ARGUS is enabled then yaim will configure ARGUS PEP clients on nodes (where supported). Otherwise ARGUS PEP client setup is skipped. The variable specifies the ARGUS resource ID to be used. The cream CE and WMS have their own node specific version of this variable, and GLEXEC on the WN is controlled by other variables. So this generic variable is not used in the configuration of those node types.	GENERAL_PEPC_RESOURCEID=urn:mysitename.org:resource:other	4.0.12-1
GLITE_EXTERNAL_ROOT	The directory where the TAR UI and TAR WN install the external dependencies. Please, check the TAR UI and TAR WN installation instructions for more details. Note that GLITE_EXTERNAL_ROOT=${INSTALL_ROOT}/external is the only configuration that has been tested.	GLITE_EXTERNAL_ROOT=${INSTALL_ROOT}/external	3.0.1-0
GLITE_USER_HOME	This variable will be deprecated in the future. From yaim-core >= 4.0.5-3 it defaults to GLITE_HOME_DIR. Please see yaim core 4.0.5-7 Known Issues if you are using yaim core <= 4.0.7-7 or yaim wms <= 4.0.5-2	GLITE_USER_HOME=/home/glite	3.0.1-0
GRIDICE_SERVER_HOST	GridIce server hostname. Only used in 3.0 configurations.	GRIDICE_SERVER_HOST=my-gridice.cern.ch	3.0.1-0
GROUPS_CONF	Path to the file containing information on the mapping between VOMS groups and roles to local groups. An example of this configuration file is given in /opt/glite/yaim/examples/groups.conf. More details can be found in the Group configuration section in the YAIM guide.	GROUPS_CONF=/opt/glite/etc/groups.conf	3.0.1-0
JOB_MANAGER	The name of the job manager used by the gatekeeper. Must be one of: lcgpbs, lcglsf, lcgsge, lcgcondor, lsf, pbs or condor. For a CREAM CE and glite-Cluster instead specify one of: pbs, lsf, sge or condor (no "lcg" version)	JOB_MANAGER=lcgpbs	3.0.1-0
LB_HOST	LB hostname. It won't be anymore mandatory for UI and VOBOX, only for WMS configuration. See more information in the variable list of each node type	LB_HOST=yaim-lb.cern.ch	3.0.1-0
LOCAL_GROUPS_CONF	Optional variable to specify a local groups.conf. It is similar to GROUPS_CONF but used to specify a separate file where local accounts specific to the site are defined. More details can be found in the Group configuration section in the YAIM guide.	LOCAL_GROUPS_CONF=/opt/glite/yaim/etc/local.conf	4.0.5-1
MON_HOST	RGMA hostname.	MON_HOST=yaim-mon.cern.ch	3.0.1-0
MYSQL_PASSWORD	The mysql root password. Define it only if you are installing a mysql server.	MYSQL_PASSWORD=password	3.0.1-0
PX_HOST	Myproxy hostname.	PX_HOST=yaim-px.cern.ch	3.0.1-0
QUEUES	The name of the queues defined in the CE	QUEUES="dteam atlas"	3.0.1-0
<queue-name>_GROUP_ENABLE	Space separated list of VO names and VOMS FQANs which are allowed to access the queue.	DTEAM_GROUP_ENABLE="dteam /dteam/Higgs /dteam/ROLE=production"	3.0.1-0
RB_HOST	Resource Broker hostname.	RB_HOST=yaim-rb.cern.ch	3.0.1-0
RFIO_PORT_RANGE	Optional variable for the rfio port range	RFIO_PORT_RANGE="20000,25000"	3.0.1-0
SE_GRIDFTP_LOGFILE	Variable necessary to configure the gridview client on the SEs. It sets the location and filename of the gridftp server logfile on the different types of SEs.	SE_GRIDFTP_LOGFILE=/var/log/dpm-gsiftp/dpm-gsiftp.log	4.0.3-9
SE_LIST	A space separated list of SE hostnames available at your site	SE_LIST="dpm.cern.ch castor.cern.ch"	3.0.1-0
SE_MOUNT_INFO_LIST	This YAIM variable is used to set the GlueCESEBindMountInfo attribute for each defined SE. The variable is a space separated list of SE hosts from SE_LIST with the export directory from the Storage Element and the mount directory common to worker nodes part of the Computing Element like SE1:export_dir1,mount_dir1. If any SE from SE_LIST doesn't support he mount concept, don't define anything for that SE in this variable. If this is the case for all the SEs in SE_LIST, put the value none. The GlueCESEBindMountInfo will be in both cases "n.a". Please, note that in the way the glue schema is specified, a SE can only have one mount point. See also Bug 54530 affecting this variable.	SE_MOUNT_INFO_LIST="se1.cern.ch:/data/atlas,/storage/atlas se2.cern.ch:/data/dteam,/storage/dteam"	4.0.7-1
SITE_BDII_HOST	The site BDII host name	SITE_BDII_HOST=yaim-site.cern.ch	4.0.0
SITE_EMAIL	This YAIM variable is used to set the GlueSiteEmailContact attribute. It's the main email contact for the site. The syntax is a coma separated list of email addresses.	SITE_EMAIL=yaim-contact@cern.ch,admin-yaim@cern.ch	3.0.1-0
SITE_HTTP_PROXY	Optional variable to specify whether your site has an http proxy (syntax is as that of the http_proxy environment variable). It will be used in config_crl and used by the cron jobs (http_proxy) in order to reduce to load on the CA host.	SITE_HTTP_PROXY="http-proxy.my.domain	3.0.1-0
SITE_INFO_VERSION	Optional variable to specify the version of the set of configuration files (site-info.def, vo.d/, group.d/, nodes/ and local functions) that the sys admin can package under one rpm. It's in fact the rpm version. This variable is used when executing the option -p of the yaim command. Note that this variable has to be defined in site-info.def and not in any other configuration file in the siteinfo directory.	SITE_INFO_VERSION=1.1	4.0.3-5
SITE_LAT	This YAIM variable is used to set the GlueSiteLatitude attribute. It's the position of the site north or south of the equator measured from -90º to 90º with positive values going north and negative values going south.	SITE_LAT=46.20	3.0.1-0
SITE_LONG	This YAIM variable is used to set the GlueSiteLongitude attribute. It's the position of the site east or west of Greenwich, England measured from -180º to 180º with positive values going east and negative values going west.	SITE_LONG=6.1	3.0.1-0
SITE_NAME	This YAIM variable is used to set the GlueSiteName attribute. It's the human-readable name of your site.	SITE_NAME=yaim-testbed	3.0.1-0
SPECIAL_POOL_ACCOUNTS	Optional variable. It determines the use of pool accounts for special users when generating the grid-mapfile. If not defined, YAIM will decide whether to use special pool accounts or not automatically. The value is yes or no	SPECIAL_POOL_ACCOUNTS=yes	4.0.5-1
USE_ARGUS	Optional variable. When set to yes indicates that setup of the ARGUS authorisation framework is to be done. A number of other variables are required to fully specify the ARGUS parameters and allow the configuration to be made. See the "ARGUS authorisation framework control" section in the definition file, where the variables are grouped together. Currently the enabling of ARGUS on the WN is independent of this option.	USE_ARGUS=no	4.0.12-1
USER_HOME_PREFIX	Optional variable used to specify a home directory for the pool accounts different from /home. The directory must exist in the system. YAIM is not creating it. If it doesn't exist, when trying to add the users, the yaim command will fail. So sys admins must ensure the directory specified by this variable already exists. See below in the VO related variables the usage of this variable per VO. If the variable is defined for a certain VO, that value will have priotity over this one.	USER_HOME_PREFIX=/special/dir/	4.0.4-1
USERS_CONF	Path to the file containing the list of Linux users (pool accounts) to be created. This file should be created by the site administrator. It contains a plain list of the users and their IDs. An example of this configuration file is given in /opt/glite/yaim/examples/users.conf. More details can be found in the User configuration section in the YAIM guide.	USERS_CONF=/opt/glite/yaim/etc/users.conf	3.0.1-0
VOS	List of supported VOs	VOS="dteam atlas"	3.0.1-0
VO_SW_DIR	Base directory for installation of the experiment software. It's normally used in combination of a VO related variable.	VO_SW_DIR=/opt/exp_soft	3.0.1-0
WMS_PEPC_RESOURCEID	If specified and configuration of ARGUS PEP client is enabled then yaim will configure ARGUS on the WMS, otherwise ARGUS setup is skipped on that node. The variable specifies the ARGUS resource ID to be used.	WMS_PEPC_RESOURCEID=urn:mysitename.org:resource:wms	4.0.12-1
WN_LIST	Path to the list of Worker Nodes. The list of Worker Nodes is a file to be created by the site administrator. An example of this configuration file is given in /opt/glite/yaim/examples/wn-list.conf. For more information please check the WN list section in the YAIM guide.	WN_LIST=/opt/glite/yaim/etc/wn.conf	3.0.1-0

VO related variables

Note : Exceptionally, LCG VOs have VO related variables distributed in site-info.def. For EGEE VOs, it's recommendable that sys admin check the CIC portal VO Id card information to know which values they should use to configure their VO related variables.

Note that <vo-name> should be in capital letters and in case '.' and '-' are part of the vo name, they should be transformed into '_'. For example, a vo called org.yaim.vo should define its variables as VO_ORG_YAIM_VO_NAME_*. For more information on VO variables please check the vo.d directory section in the YAIM guide.

site-info.pre

Variable name	Description	Default value	YAIM version >=
BATCH_BIN_DIR	The path of the lrms commands	/usr/bin	3.0.1-0
BDII_ARCHIVE_SIZE	It is the number of dumps of the database to keep for debugging purposes. This variable is actually taken into account when using BDII version 5.	0	4.0.8-1
BDII_BREATHE_TIME	It is the time in seconds between updates of the bdii.	120	4.0.8-1
BDII_GROUP	BDII user group	edguser	4.0.5-1
BDII_HOME_DIR	BDII user home directory. Note: It is recommendable to use /var/lib/user_name as HOME directory for system users.	/home/edguser	4.0.10-1
BDII_PASSWD	This is the password for the LDAP database used by the bdii. This variable is actually taken into account when using BDII version 5.	$(mkpasswd -s 0)	4.0.8-1
BDII_READ_TIMEOUT	It is the amount of time to wait until an information is assumed to have timed out. This variable is actually taken into account when using BDII version 5.	300	4.0.8-1
BDII_RESOURCE_TIMEOUT	The timeout value to be used with a resource BDII. It is the time the BDII will wait when running the GIP	$BDII_SITE_TIMEOUT - 5	3.0.1-0
BDII_SITE_TIMEOUT	The timeout value to be used with a site BDII. It is the time the BDII will wait when querying resource BDIIs or GRISs	120	3.0.1-0
BDII_USER	BDII user	edguser	4.0.5-1
CA_REPOSITORY	APT repository containing the string to install the Certification Authorities files. Used by the TAR UI	rpm http://linuxsoft.cern.ch/ LCG-CAs/current production	3.0.1-0
CONFIG_GRIDMAPDIR	It enables or disables the creation of the gridmap directory.	yes (See more details in case you are configuring GLEXEC_wn)	4.0.11-1
CONFIG_USERS	The creation of groups and users needed by the middleware is done by YAIM. The default value is yes. If you want to disable this functionality set it to no. You must ensure the users and groups defined in $INSTALL_ROOT/glite/yaim/examples/edgusers.conf are created in your system. For the VO pool accounts, YAIM provides also an example file in INSTALL_ROOT/glite/yaim/examples/users.conf. Even if you create your own users, you must provide a similar file that will be used to create the gridmap file.	yes	4.0.5-1
CRON_DIR	Directory where YAIM writes all the cron jobs	/etc/cron.d	3.0.1-0
DPMMGR_USER	DPM user	dpmmgr	4.0.5-1
DPMMGR_GROUP	DPM user group	dpmmgr	4.0.5-1
EDG_WL_SCRATCH	Optional scratch directory for jobs	""	3.0.1-0
EDG_USER	edg user	edguser	4.0.5-1
EDG_GROUP	edg user group	edguser	4.0.5-1
EDG_HOME_DIR	edg user home directory. Note: It is recommendable to use /var/lib/user_name as HOME directory for system users.	/home/edguser	4.0.10-1
EDGINFO_USER	edginfo user	edginfo	4.0.5-1
EDGINFO_GROUP	edginfo user group	edginfo	4.0.5-1
EDGINFO_HOME_DIR	edg user home directory. Note: It is recommendable to use /var/lib/user_name as HOME directory for system users.	/home/edginfo	4.0.10-1
FQANVOVIEWS	If set to yes yaim will configure the infosystem to publish the CE VOViews also for groups maped/identified by a VOMS FQANS. If set to no then only the VO VOViews will be published. If you want to know more on how the publication mechanism of VOViews works read this.	no	4.0.4-1
FUNCTIONS_DIR	The directory where YAIM functions are stored	/opt/glite/yaim/functions	3.0.1-0
GIP_CACHE_TTL	How long information in the cache is valid.	300	3.0.1-0
GIP_FRESHNESS	If the information from the plug-ins is within this timelimit, the dynamics plug-ins will not be executed.	60	3.0.1-0
GIP_RESPONSE	How long the GIP will wait for dynamic plug-ins to run before reading the information from the cache.	$BDII_SITE_TIMEOUT - 5	3.0.1-0
GIP_TIMEOUT	The timeout value to be used with dynamic plug-ins.	150	3.0.1-0
GLITE_USER	glite user	glite	4.0.5-1
GLITE_GROUP	glite user group	glite	4.0.5-1
GLITE_HOME_DIR	glite user home directory	/home/glite	4.0.5-1
GLOBUS_TCP_PORT_RANGE	Port range for Globus IO. It should be specified as "num1,num2". YAIM automatically handles the syntax of this variable depending on the version of VDT. If it's VDT 1.6 it leaves "num1,num2". If it's a version < VDT 1.6 it changes to "num1 num2"	"20000,25000"	3.0.1-0
GRIDFTP_CONNECTIONS_MAX	Maximum number of simultaneous connections to the gridftp server. This default is increased to 150 in yaim core >= 4.0.10-1. It's actually recommendable to increase this variable to a number 2/3 times higher than its default of 50 for yaim core <= 4.0.6-1	150	4.0.6-1
INSTALL_ROOT	Installation root - change if using the re-locatable distribution.	/opt	3.0.1-0
INFOSYS_GROUP	Information system user group	infosys	4.0.5-1
JAVA_LOCATION	Path to Java VM installation. It can be used in order to run a different version of java installed locally. WARNING! This variable will dissappear soon	/usr/java/j2sdk1.4.2_12	Deprecated in glite-yaim-core >= 4.0.8-1
LCMAPS_DEBUG_LEVEL	LCMAPS debugging level	0	4.0.1-4
LCMAPS_LOG_LEVEL	LCMAPS logging level	1	4.0.1-4
LCAS_DEBUG_LEVEL	LCAS debugging level	0	4.0.1-4
LCAS_LOG_LEVEL	LCAS logging level	1	4.0.1-4
LCG_REPOSITORY	APT repository for the EGEE middleware. This is only for gLite 3.0 that uses apt. For gLite 3.1, please check this link.	'rpm http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/ rhel30 externals Release3.0 updates'	3.0.1-0
LFCMGR_USER	LFC user	lfcmgr	4.0.5-1
LFCMGR_GROUP	LFC user group	lfcmgr	4.0.5-1
MY_DOMAIN	The site's domain name.	hostname -d	3.0.1-0
ORACLE_LOCATION	The location of the oracle client libraries	/usr/lib/oracle/10.2.0.3	3.0.1-0 (value updated in 4.0.6-1)
OUTPUT_STORAGE	Default Output directory for the jobs.	/tmp/jobOutput	3.0.1-0
REG_HOST	RGMA Registry hostname.	lcgic01.gridpp.rl.ac.uk	3.0.1-0
REPOSITORY_TYPE	It can only be apt. Moreover, this is only valid for gLite 3.0. For gLite 3.1 please visit this link	apt	3.0.1-0
RGMA_USER	RGMA user	rgma	4.0.5-1
RGMA_GROUP	RGMA user group	rgma	4.0.5-1
SE_ARCH	"disk, tape, multidisk, other" It populates GlueSEArchitecture.	multidisk	3.0.1-0
TOMCAT_USER	tomcat user	tomcat	4.0.8-1
TRUSTMANAGER_CRL_UPDATE_INTERVAL	This variable is used in the trustmanager configuration and it defines how often the X509_CERT_DIR is polled for changes in the files. It's a number followed by h,m or s time units.	2h	4.0.8-1
UNPRIVILEGED_MKGRIDMAP	Note that this variable should be specified per VO in yaim core >= 4.0.10-1 !!! In case you want to create a grid-map file which only contains mappings to ordinary users. no will create a grid-map file with special users as well, if defined in groups.conf. yes, will create a grid-mapfile containing only mappings to ordinary pool accounts.	no	4.0.6-1
YAIM_LOGGING_LEVEL	The logging level to print debugging information. Possible values are NONE, ABORT, ERROR, WARNING, INFO, DEBUG.	INFO	3.0.1-0

site-info.post

Service configuration variables

NOTE: Some yaim modules have started to distribute node specific variables that in some cases used to be part of site-info.def. This documentation already describes the situation where all node specific variables are distributed by the corresponding yaim module. Remember that this is not yet the current situation for all yaim modules, so maybe some of the files described here do not exist yet in the yaim module.

In order to configure a service you would need to define some variables distributed in different files. You can define these variables in your site-info.def or leave them under siteinfor/services directory, where siteinfo is the directory where your site-info.def is located. Default variables can be redefined as well in one of the two locations.

The files where the variables are located are:

• Mandatory general variables: sys admins must define these variables. They can be found in opt/glite/yaim/examples/siteinfo/site-info.def and are described in the previous section site-info.def variables.
• Mandatory service specific variables: sys admins must define these variables. They can be found in opt/glite/yaim/examples/siteinfo/services/node-type and are described in the following sections.
• Default general variables: sys admins don't need to define these variables unless they want a specific value for their site which is different from the default one. They can be found in opt/glite/yaim/defaults/site-info.pre or post and are described in the previous section site-info.pre variables and site-info.post.
• Default service specific variables: sys admins don't need to define these variables unless they want a specific value for their site which is different from the default one. They can be found in opt/glite/yaim/defaults/node-type.pre or post and are described in the following sections.

All the services need to have INSTALL_ROOT defined. This variable is always defined in site-info.pre and defaults to /opt.

AMGA

AMGA oracle

• Mandatory general variables
  • VOS

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-amga_oracle.

AMGA postgres

• Mandatory general variables
  • VOS

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-amga_postgres.

APEL

• Mandatory general variables
  • APEL_DB_PASSWORD
  • CE_HOST
  • MON_HOST
  • MYSQL_PASSWORD
  • SITE_NAME

• Default service specific variables: can be found in /opt/glite/yaim/defaults/glite-apel.pre:

ARGUS

• Mandatory general variables
  • GROUPS_CONF
  • USERS_CONF
  • VOS

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-authz_server.

• Default service specific variables: they can be found in /opt/glite/yaim/default/glite-authz_server.pre/post:

BDII

site BDII

• Mandatory general variables
  • CE_HOST
  • SITE_BDII_HOST
  • SITE_EMAIL
  • SITE_LAT
  • SITE_LONG
  • SITE_NAME

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/services/siteinfo/glite-bdii_site:

Variable Name	Description	Value type	Version
BDII_REGIONS	List of host identifiers publishing information to the BDII. For each item listed in the BDII_REGIONS variable you need to create a BDII_<host-id>_URL variable</host-id>	node-type name	3.0.1-0
BDII_<host-id>_URL	URL of the information producer (e.g. BDII_host1_URL="ldap://host1_hostname:2170/mds-vo-name=resource,o=grid". Where host1 is a host where several node types may be installed, for example a lcg CE and a site BDII. It's therefore not necessary to create one variable per node type, but per host)	URL(*)	3.0.1-0
SITE_DESC	Long format Name of your site	"A long format name of your site"	glite-yaim-bdii 4.0.4-2
SITE_LOC	Location of the site BDII	"City, Country"	3.0.1-0
SITE_OTHER_GRID	Grid to which your site belongs to, i.e. WLCG or EGI. Use | to separate values.	Grid project name	glite-yaim-bdii 4.0.4-4
SITE_OTHER_*	For more details, please visit https://wiki.egi.eu/wiki/MAN1_How_to_publish_Site_Information	SITE_OTHER_GRID="WLCG|EGI"	glite-yaim-bdii 4.0.4-2
SITE_SECURITY_EMAIL	Contact email for security	e-mail address	glite-yaim-bdii 4.0.4-2
SITE_SUPPORT_EMAIL	The site user support e-mail address as published by the information system	e-mail address	3.0.1-0
SITE_SUPPORT_SITE	Support entry point. Unique Id for the site in the GOC DB and information system	my-bigger-site.their-domain	Deleted >= glite-yaim-bdii 4.0.4-2
SITE_TIER	Site tier	URL	Deleted >= glite-yaim-bdii 4.0.4-2
SITE_WEB	Site web site	TIER 1 or TIER 2	3.0.1-0

(*) The URL is in the form of ldap://information_producer_host_name:2170/mds-vo-name=resource,o=grid.

top BDII

• Mandatory general variables
  • BDII_HOST
  • SITE_NAME

• Default service specific variables: they can be found in in /opt/glite/yaim/defaults/glite-bdii_top.pre:

CLUSTER

Please, check this twiki page for more details.

• Mandatory service specific variables: They can be found in /opt/glite/yaim/examples/siteinfo/services/glite-cluster:

The new variable names follow this syntax:

• In general, in variables based on hostnames, queues or VOViews the characters '.' and '-' must each be replaced with '_'
• <host-name>: identifier that corresponds to the CE hostname in lower case. Example: ctb-generic-1.cern.ch -> ctb_generic_1_cern_ch
• <cluster-identifier>: identifier that corresponds to the cluster identifier in upper case. Example: my_cluster -> MY_CLUSTER
• <subcluster-identifier>: identifier that corresponds to the subcluster identifier in upper case. Example: my_subcluster -> MY_SUBCLUSTER

Most of these variables correspond to variables that are defined for a CE when it is deployed in non-cluster mode. Please refer to the description of the old variable where applicable as shown in the table below.

"sw1 [| sw2 [| ...]"

CONDOR

CONDOR server

The Condor Server is a glite-WN configured as a Batch Server for condor. The list of variables needed to configure it are:

• glite-WN variables: Variables for glite-WN.

• Mandatory general variables: with the following meaning for CONDOR:

CONDOR client

The Condor Client is a Worker Node configured as an Executer for condor. You need the same variables used for the Condor Server configuration.

CONDOR Utils

The Condor Utils is a lcg-CE or creamCE configured as Job submitter for condor. It also provides the information to be published via the site BDII and parses the accounting data to the APEL database located at the MON_HOST. The list of variables needed to configure it are:

• cream CE variables: Variables for cream-CE.
• lcg CE variables: Variables for lcg-CE.
• Mandatory general variables: with the following meaning for CONDOR:

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/services/glite-condor-utils.

Variable Name	Description	Value type	Example	Version
CONDOR_ARCH	Architeqture of the condor pool	String	INTEL	4.0.0-1
CONDOR_OS	Operation system of the condor pool	String	LINUX	4.0.0-1

NOTE: There are no queues in the "conventional" sense in condor. Set the variable QUEUES to the short hostname of the condor server (e.g. QUEUES=condor). Then set the variable ${QUEUES}_GROUP_ENABLE accordingly to your access policy to the condor pool, e. g. as you would do in PBS.

• Default general variables: with the following meaning for CONDOR:

• List of daemons started by YAIM: (Results of the command ps aux | grep condor)

Condor Server

• condor_master
• condor_collector
• condor_negotiator

Condor Client

• condor_master
• condor_startd

Condor Utils

• condor_master
• condor_schedd

• List of cron jobs configured by YAIM

cream CE

For more details about the cream CE configuration, please check the CREAM CE SystemAdminitrator guide.

There is a tool that checks your cream CE configuration.

• Mandatory general variables

• • BATCH_LOG_DIR (for Torque/PBS, this must be set to the directory "containing" the server_logs directory; usually /var/torque)
  • BATCH_SERVER
  • BDII_HOST
  • CE_BATCH_SYS
  • CE_CAPABILITY (mandatory for yaim-cream-ce >= 4.0.9-3)
  • CE_CPU_MODEL
  • CE_CPU_SPEED
  • CE_CPU_VENDOR
  • CE_HOST
  • CE_INBOUNDIP
  • CE_LOGCPU
  • CE_MINPHYSMEM
  • CE_MINVIRTMEM
  • CE_OS
  • CE_OTHERDESCR (mandatory for yaim-cream-ce >= 4.0.9-3)
  • CE_SMPSIZE
  • CE_OS_RELEASE
  • CE_OS_VERSION
  • CE_OS_ARCH
  • CE_OUTBOUNDIP
  • CE_PHYSCPU
  • CE_RUNTIMEENV
  • CE_SF00
  • CE_SI00
  • GROUPS_CONF
  • <queue-name>_GROUP_ENABLE</queue-name>
  • JOB_MANAGER
  • SE_LIST
  • SE_MOUNT_INFO_LIST (mandatory for yaim-cream-ce >= 4.0.8-2)
  • USERS_CONF
  • QUEUES
  • VOS
  • VO_<vo-name>_SW_DIR
  • VO_<vo-name>_VOMS_SERVERS
  • VO_<vo-name>_VOMSES

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-creamce:

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-creamce.pre or /opt/glite/yaim/defaults/glite-creamce.post:

• List of daemons started by YAIM: (Results of the command ps aux)
  • /usr/sbin/slapd
  • /opt/bdii/sbin/bdii-update
  • bdii-fwd
  • /opt/globus/sbin/globus-gridftp-server
  • /opt/glite/bin/BLParserPBS
  • /opt/glite/bin/blahpd
  • /bin/sh /opt/glite/etc/glite-ce-cream/blah.sh
  • /opt/glite/bin/glite-lb-logd
  • /opt/glite/bin/glite-lb-interlogd
  • tomcat5 server

• List of cron jobs configured by YAIM There are logrotation, poolaccount cleaning, crl fetching

dCache

For dCache configuration variables, please check the dCache web page.

DPM

As soon as the fix for 40625 is released, DPM specific variables will be found in the yaim dpm module.

DPM head mysql

• Mandatory general variables
  • BDII_HOST
  • DPM_HOST
  • GROUPS_CONF
  • MYSQL_PASSWORD
  • SE_LIST
  • SITE_EMAIL
  • SITE_NAME
  • SE_GRIDFTP_LOGFILE
  • USERS_CONF
  • VOS
  • VO_<vo-name>_SW_DIR
  • VO_<vo-name>_VOMS_SERVERS
  • VO_<vo-name>_VOMS_CA_DN
  • VO_<vo-name>_VOMSES

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/services/siteinfo/glite-se_dpm_mysql:

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-se_dpm_mysql.pre:

DPM disk

• Mandatory general variables
  • BDII_HOST
  • DPM_HOST
  • GROUPS_CONF
  • SE_GRIDFTP_LOGFILE
  • SE_LIST
  • USERS_CONF
  • VOS
  • VO_<vo-name>_SW_DIR
  • VO_<vo-name>_VOMS_SERVERS
  • VO_<vo-name>_VOMS_CA_DN
  • VO_<vo-name>_VOMSES

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-se_dpm_disk :

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-se_dpm_disk.pre:

E2EMONIT

• Mandatory general variables
  • MON_HOST

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/services/siteinfo/glite-e2emonit:

• Default general variables
  • REG_HOST

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-e2emonit.pre:

FTA

For more details, please check: FTS YAIM reference

• Mandatory general variables
  • BDII_HOST
  • FTS_HOST_ALIAS
  • GROUPS_CONF
  • MON_HOST
  • PX_HOST
  • SITE_NAME
  • USERS_CONF
  • VOS

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-fta2:

For a detailed list of optional parameters in FTA configuration, please check the links at the beginning of this section.

• Default general variables
  • ORACLE_LOCATION
  • REG_HOST

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-fta2.pre:

FTM

For more details, please check the File Transfer Monitor wiki.

• Mandatory general variables
  • BDII_HOST
  • GROUPS_CONF
  • FTS_HOST_ALIAS
  • PX_HOST
  • USERS_CONF

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-ftm2:

• Default general variables
  • ORACLE_LOCATION

FTS

For more details, please check: FTS YAIM reference

• Mandatory general variables
  • BDII_HOST
  • FTS_HOST_ALIAS
  • GROUPS_CONF
  • MON_HOST
  • PX_HOST
  • SITE_NAME
  • USERS_CONF
  • VOS
  • VO_<vo-name>_VOMS_SERVERS
  • VO_<vo-name>_VOMS_CA_DN
  • VO_<vo-name>_VOMSES

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-fts2:

• Default general variables
  • ORACLE_LOCATION
  • REG_HOST

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-fts2.pre:

GLEXEC_wn

• Mandatory general variables:
  • VOS
  • USERS_CONF

• Default general variables:
  • X509_VOMS_DIR
  • X509_CERT_DIR
  • GRIDMAPFILE
  • GROUPMAPFILE
  • CONFIG_USERS
  • EDG_GROUP

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-glexec_wn:

Variable Name	Description	Value type	Version
GLEXEC_WN_OPMODE	Define this variable to configure the operation mode of glexec in your WN. The possible values are: 1) setuid: it will actually enable glexec to do the identity change. 2) log-only : it won't do any identity change but the log files will show if the mapping was succesful or not.	String	4.0.5-1
GLEXEC_WN_SCAS_ENABLED	Define this variable to configure glexec to work against a SCAS server. 'yes' means you want to use a SCAS server and therefore you need to define; 'no' means you don't want to use any SCAS server. See also the notes below.	String	4.0.5-1
GLEXEC_WN_ARGUS_ENABLED	Define this variable to configure glexec as a PEP client (see the EGEE/AuthorizationFramework); 'yes' means use ARGUS, 'no' means do not use ARGUS. See also the notes below.	String	N/A
SCAS_HOST	SCAS server hostname. Define this variable if you want to configure glexec to work against a SCAS server.	hostname	4.0.5-1
SCAS_PORT	SCAS port where the SCAS server is listening. Define this variable if you want to configure glexec to work against a SCAS server.	port	4.0.5-1
SCAS_ENDPOINTS	complete URL of SCAS endpoint, e.g. https://scas1.example.com:8443. Alternative to using SCAS_HOST and SCAS_PORT. Multiple values are allowed, separated by whitespace	URL	N/A
ARGUS_PEPD_ENDPOINTS	If glexec is a PEP client, define the PEPD endpoint with this variable. It currently supports only one endpoint and should be a URLs, e.g. https://argus1.example.com:8154/authz	URL	N/A

• Optional service specific variables: they can be found in /opt/glite/yaim/siteinfo/services/glite-glexec_wn:

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-glexec_wn.pre or post:

Notes on using SCAS and ARGUS

Although untypical, it is possible to configure both the SCAS and ARGUS modules as back-ends for LCMAPS. The resulting configuration will first do the callout to ARGUS, then SCAS. It may be useful, e.g. if you want ARGUS to perform global banning and SCAS for account mapping.

In the following examples we show entries for users.conf and groups.conf needed by the GLEXEC_wn cofiguration. We use PILOT_JOB_FLAG=pilot, but you can choose a different identifier. We've chosen the dteam VO but you should change it to the VOs you support.

Example of users.conf file where user accounts for pilot jobs are defined:

55401:pildtm01:1473,2688:dteampil,dteam:dteam:pilot
55402:pildtm02:1473,2688:dteampil,dteam:dteam:pilot
55403:pildtm03:1473,2688:dteampil,dteam:dteam:pilot
...

Example of groups.conf file where FQANs for pilot jobs are defined:

"/dteam/ROLE=pilot":::pilot:

Please, take into account that:

• User accounts for pilot jobs should be pool accounts since static accounts are not supported.
• The flag you define in PILOT_JOB_FLAG should be the same as the flag you specify in users.conf and groups.conf.
• For more information in users.conf please check the YAIM guide - users.conf section and for groups.conf check YAIM guide - groups.conf section.
• Bear in mind that you need to contact your VO to know which FQAN is supported for pilot jobs. If you define role pilot in your configuration but this is not defined in the corresponding VO, it will be useless. This information should be part of the VO ID Card, otherwise please contact the VO.

HYDRA

For more information on the HYDRA service, please check this link.

• Mandatory general variables
  • MYSQL_PASSWORD

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-hydra:

Some configuration guidelines:

• Usually at least three different institutions in the same VO are needed for a production hydra installation
• For production use you should always configure only one local instance per (e.g. HYDRA_INSTANCES=1) server and confgiure the following variables for it
  • HYDRA_DBNAME, HYDRA_DBUSER, HYDRA_DBPASSWORD, HYDRA_ADMIN (can be e.g. admin user cert, or hostcert DN), HYDRA_CREATE
• Then you should configure (usually at least two) additional servers (e.g. HYDRA_PEERS="2 3"), with the following variables
  • HYDRA_CREATE, HYDRA_HOST and HYDRA_ID
• You can configure three different Hydra instance on one server, but this should be solely for testing purposes! In this case you configure three local instances (e.g. HYDRA_INSTANCES="1 2 3")
  • Configure these three instances like local instances
  • Do not configure any HYDRA_PEERS
• More configuration examples in the above linked to documentation

LB

• Mandatory general variables
  • MYSQL_PASSWORD
  • SITE_NAME

• Default general variables
  • REG_HOST

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-lb.pre:

Note: Use GLITE_LB_SUPER_USERS instead of GLITE_LB_WMS_DN in older versions.

lcg CE

• Mandatory general variables
  • BATCH_SERVER
  • BDII_HOST
  • CE_BATCH_SYS
  • CE_CAPABILITY (mandatory for yaim-lcg-ce >= 4.0.5-4)
  • CE_OTHERDESCR (mandatory for yaim-lcg-ce >= 4.0.5-4)
  • SE_MOUNT_INFO_LIST (mandatory for yaim-lcg-ce >= 4.0.5-4)
  • GROUPS_CONF
  • <queue-name>_GROUP_ENABLE
  • JOB_MANAGER
  • MON_HOST
  • QUEUES
  • SE_LIST
  • USERS_CONF
  • VOS
  • VO_<vo-name>_VOMS_SERVERS
  • VO_<vo-name>_SW_DIR
  • VO_<vo-name>_VOMS_CA_DN
  • VO_<vo-name>_VOMSES

• Also required for lcg-CE in non cluster mode (i.e. all lcg-CE <= 3.1.40)
  • CE_RUNTIMEENV
  • CE_SMPSIZE
  • CE_OS_ARCH
  • CE_SF00
  • CE_SI00
  • CE_MINPHYSMEM
  • CE_MINVIRTMEM
  • CE_INBOUNDIP
  • CE_OUTBOUNDIP
  • CE_OS
  • CE_OS_RELEASE
  • CE_OS_VERSION
  • CE_CPU_SPEED
  • CE_CPU_MODEL
  • CE_CPU_VENDOR
  • CE_PHYSCPU
  • CE_LOGCPU

• cluster mode with lcg-CE>=3.1.46 is selected by defining
  • LCGCE_CLUSTER_MODE=yes

• New Mandatory variables exist for the lcg-CE >= 3.1.46 when in cluster mode, although many of the CE_ yaim variables above are no longer needed (but are set in new variables when configuring the glite-CLUSTER node). Variables which are required in cluster mode are described in the following paragraphs and one can also find lists of variables which are available in the example /opt/glite/yaim/examples/siteinfo/services/lcg-ce

When the lcg-CE is configured in cluster mode it will stop publishing information about clusters and subclusters. That information should be published by the glite-CLUSTER node type instead. The glite-CLUSTER may be installed on the same machine as the lcg-CE or on a different host. A new set of yaim variables has been defined for configuring the information which is still required by the lcg-CE in cluster mode. Follow the instructions below:

The new variable names follow this syntax:

• In general, variables based on hostnames, queues or VOViews containing '.' and '_' # should be transformed into '-'
• <host-name>: identifier that corresponds to the CE hostname in lower case. Example: ctb-generic-1.cern.ch -> ctb_generic_1_cern_ch
• <queue-name>: identifier that corresponds to the queue in upper case. Example: dteam -> DTEAM
• <voview-name>: identifier that corresponds to the VOView id in upper case. '/' and '=' should also be transformed into '_'. Example: /dteam/Role=admin -> DTEAM_ROLE_ADMIN

The following variables will be distributed in the future in site-info.def since they affect other yaim modules. At this moment we are in a transition phase to migrate to the new variable names.

When using yaim-core >= 4.0.13 the OLD variables JOB_MANAGER, _GROUP_ENABLE and QUEUES will be set (or reset) to the values of the new replacement variables listed above. With prior versions the new and the old style need to both be set consistently.

• Optional service specific variables: /opt/glite/yaim/examples/siteinfo/services/lcg-ce:

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/lcg-ce.post:

LFC

As soon as the fix for bug 40619 is released, LFC specific variables can be found in the yaim lfc module.

LFC mysql

• Mandatory general variables
  • GROUPS_CONF
  • MYSQL_PASSWORD
  • SITE_NAME
  • USERS_CONF
  • VOS
  • VO_<vo-name>_VOMS_SERVERS
  • VO_<vo-name>_VOMS_CA_DN
  • VO_<vo-name>_VOMSES

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-lfc_mysql:

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-lfc_mysql.pre:

Variable Name	Description	Value type	Default Value	Version
LFC_DB	The LFC DB name	String	cns_db	3.0.1-0
LFC_DB_HOST	The LFC DB host name	String	$LFC_HOST (does not work: BUG:76322)	3.0.1-0
LFC_DB_PASSWORD	The LFC DB user password.	String	mypassword	3.0.1-0
LFC_HOST_ALIAS	If you use a DNS alias in front of your LFC, specify it here.	FQDN	""	3.0.1-0
LFC_CENTRAL	List of VO names whose catalog is configured as central.	Space separated VO list	""	3.0.1-0
LFC_LOCAL	List of VO names whose catalog is configured as local. (do _not_ rely on the default behavior, it has bugs)	Space separated VO list	""	3.0.1-0

LFC oracle

• Mandatory general variables
  • GROUPS_CONF
  • SITE_NAME
  • USERS_CONF
  • VOS
  • VO_<vo-name>_VOMS_SERVERS
  • VO_<vo-name>_VOMS_CA_DN
  • VO_<vo-name>_VOMSES

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-lfc_oracle:

• Default general variables
  • ORACLE_LOCATION

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-lfc_oracle.pre:

Variable Name	Description	Value type	Default Value	Version
LFC_DB	The Oracle db user	String	LCG_YAIM	3.0.1-0<
LFC_DB_HOST	The Oracle connect service name	String	$LFC_HOST (does not work: BUG:76322)	3.0.1-0<
LFC_DB_PASSWORD	The Oracle db user password. Cannot contain @ sign	String	mypassword	3.0.1-0<
LFC_HOST_ALIAS	If you use a DNS alias in front of your LFC, specify it here.	FQDN	""	3.0.1-0
LFC_CENTRAL	List of VO names whose catalog is configured as central.	Space separated VO list	""	3.0.1-0
LFC_LOCAL	List of VO names whose catalog is configured as local. (do _not_ rely on the default behavior, it has bugs)	Space separated VO list	""	3.0.1-0

LSF utils

• Mandatory general variables
  • APEL_DB_PASSWORD
  • BATCH_SERVER
  • CE_BATCH_SYS
  • CE_HOST
  • MON_HOST
  • SITE_NAME

MON

• Mandatory general variables
  • APEL_DB_PASSWORD
  • CE_HOST
  • GRIDICE_SERVER_HOST
  • MON_HOST
  • MYSQL_PASSWORD
  • SITE_NAME
  • SITE_BDII_HOST

If GIN_BDII is yes, then SITE_BDII_HOST is required (default behaviour). Otherwise, GRIDICE_SERVER_HOST is required.

• Default general variables
  • REG_HOST
  • JAVA_LOCATION (will disappear in a future release)

• Default service specific variables: can be found in /opt/glite/yaim/defaults/glite-mon.pre:

MPI

For more information, please check the YAIM MPI wiki.

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-mpi:

NAGIOS

• For more information about Nagios configuration with YAIM, please check the Grid Monitoring Yaim Tutorial.

PX

• Mandatory general variables
  • SITE_NAME
  • PX_HOST

• Mandatory service specific variables: /opt/glite/yaim/examples/services/glite-px:

For a better understanding of the configuration variables, please, check the official Myproxy documentation or the relevant section of the myproxy.conf file.

RB

• Mandatory general variables
  • BATCH_LOG_DIR
  • BDII_HOST
  • GRIDICE_SERVER_HOST
  • GROUPS_CONF
  • MYSQL_PASSWORD
  • RB_HOST
  • SITE_NAME
  • SITE_EMAIL
  • USERS_CONF
  • VOS
  • VO_<vo-name>_VOMSES

SCAS

• Mandatory general variables
  • GROUPS_CONF
  • USERS_CONF
  • VO_<vo-name>_VOMSES
  • VO_<vo-name>_VOMS_CA_DN (Mandatory for glite-yaim-core > 4.0.5-7)
  • VO_<vo-name>_VOMS_SERVERS
  • VOS

• Mandatory service specific variables: None.

• Default general variables
  • X509_HOST_CERT
  • X509_HOST_KEY
  • X509_CERT_DIR

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-scas.pre or post:

• Note: the SCAS_USER_HOME variable is optional. It will be used only if CONFIG_USERS = yes. The directory will be created if it does not exist. If not set, the system default will be used.

SGE / GE utils

• Mandatory general variables
  • APEL_DB_PASSWORD
  • BATCH_LOG_DIR = SGE accounting file>.
  • BATCH_SERVER =
  • CE_BATCH_SYS = "sge"
  • CE_HOST
  • JOB_MANAGER = "sge"
  • MON_HOST
  • MY_DOMAIN
  • QUEUES
  • SITE_NAME

• Default service specific variables: can be found in /opt/glite/yaim/defaults/glite-sge-utils.pre:

SE classic

• Mandatory general variables
  • BDII_HOST
  • USERS_CONF
  • GROUPS_CONF
  • VOS
  • SITE_NAME
  • SITE_EMAIL
  • VO_<vo-name>_STORAGE_DIR
  • SE_GRIDFTP_LOGFILE
  • CLASSIC_STORAGE_DIR.

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/services/glite-seclassic:

TAR UI

Please check this link: TAR UI Installation and Configuration.

TAR WN

Please check this link: TAR WN Installation and Configuration.

TORQUE

A note on the use of munge

Torque for EPEL/Fedora is built to use munge as of version 2.5.7. See the release notes. This means that in order to use these versions of torque, munged must be started on the server and submit hosts (i.e., CEs) with a shared secret key in /etc/munge/munge.key. It is up to the administrator to take care of the distribution of this key, but the YAIM variable MUNGE_KEY_FILE can be used to install the key from a location that can be read by YAIM at configuration time. Leaving this variable empty means that the administrator is responsible for the installation of this key before YAIM is run, or the system will be left in a non-working state. Munge is required on all node types: CEs (submit hosts), the torque head node and the worker nodes.

TORQUE server

• Mandatory general variables
  • BATCH_SERVER
  • CE_HOST
  • CE_SMPSIZE
  • USERS_CONF
  • QUEUES
  • VOS
  • WN_LIST

• Default service specific variables: can be found in /opt/glite/yaim/defaults/glite-torque-server.pre:

TORQUE client

• Mandatory general variables
  • BATCH_SERVER
  • CE_HOST.
  • CE_SMPSIZE

• Default service specific variables: can be found in /opt/glite/yaim/defaults/glite-torque-client.pre:

TORQUE utils

• Mandatory general variables
  • APEL_DB_PASSWORD
  • BATCH_SERVER
  • CE_HOST
  • MON_HOST
  • QUEUES
  • SITE_NAME
  • WN_LIST

• Default service specific variables: can be found in /opt/glite/yaim/defaults/glite-torque-utils.pre:

UI

• Mandatory general variables
  • BDII_HOST
  • LB_HOST (mandatory for glite-yaim-clients < 4.0.4-4)
  • MON_HOST (not needed anymore in gLite 3.2 UI)
  • PX_HOST
  • WMS_HOST
  • VOS
  • VO_<vo-name>_VOMSES
  • VO_<vo-name>_VOMS_CA_DN (Mandatory for glite-yaim-core > 4.0.5-7)

• Default general variables
  • OUTPUT_STORAGE

• Default service specific variables: they can be found in can be found in =/opt/glite/yaim/defaults/glite-ui.pre and post:

VOBOX

• Mandatory general variables
  • BDII_HOST
  • GROUPS_CONF
  • LB_HOST (mandatory for glite-yaim-clients < 4.0.4-4)
  • MON_HOST (not needed anymore in gLite 3.2 VOBOX)
  • PX_HOST
  • RB_HOST (only for releases < 3.2.9)
  • SITE_NAME
  • SE_LIST
  • USERS_CONF
  • VOS
  • VO_<vo-name>_VOMSES
  • VO_<vo-name>_VOMS_CA_DN (Mandatory for glite-yaim-core > 4.0.5-7)
  • VO_<vo-name>_SW_DIR
  • WMS_HOST

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-vobox:

• Default general variables
  • REG_HOST

• Default service specific variables: they can be found in can be found in /opt/glite/yaim/defaults/glite-vobox.pre:

If GSSKLOG is set to yes, remember to define the GSSKLOG_SERVER.

VOMS

IMPORTANT:

For EMI installations, please refer to the latest VOMS YAIM guide.

Database-backend independent YAIM variables

• Mandatory general variables
  • VOS

The following variables are optional. You can comment them out if you want to define it. Otherwise voms will apply a default value internally:

• Default service specific variables: can be found in can be found in /opt/glite/yaim/defaults/glite-voms.[pre|post]:

VOMS mysql specific variables

• Mandatory service specific variables: can be found in /opt/glite/yaim/examples/services/glite-voms_mysql:

• Default service specific variables: can be found in can be found in /opt/glite/yaim/defaults/glite-voms.[pre|post]:

VOMS oracle specific variables

• Mandatory service specific variables: can be found in /opt/glite/yaim/examples/services/glite-voms_oracle:

• Default service specific variables: can be found in /opt/glite/yaim/defaults/glite-voms.pre and /opt/glite/yaim/defaults/glite-voms.post:

VOMS configuration examples

MySQL backend

Below is a siteinfo and service file for a minimal VOMS mysql node configuration:

site-info.def:

MYSQL_PASSWORD="pwd"
SITE_NAME="voms-certification.cnaf.infn.it"
VOS="cert.mysql"


services/glite-voms:
VOMS_HOST=cert-voms-01.cnaf.infn.it 
VOMS_DB_HOST='localhost'
VOMS_ADMIN_SMTP_HOST=iris.cnaf.infn.it
VOMS_ADMIN_MAIL=voms.administrator@cnaf.infn.it

VO_CERT_MYSQL_VOMS_PORT=15000
VO_CERT_MYSQL_VOMS_DB_USER=cert_mysql_user
VO_CERT_MYSQL_VOMS_DB_PASS=pwd
VO_CERT_MYSQL_VOMS_DB_NAME=voms_cert_mysql_db

Oracle backend

Below is a siteinfo and service file for a minimal VOMS oracle node configuration:

siteinfo.def:

VOMS_DB_TYPE="oracle"
SITE_NAME="voms-certification.cnaf.infn.it"
VOS="cert.oracle"
ORACLE_CLIENT="/usr/lib/oracle/10.2.0.4/client64"


services/glite-voms:

VOMS_HOST=cert-voms-01.cnaf.infn.it 
VOMS_ADMIN_SMTP_HOST=iris.cnaf.infn.it
VOMS_ADMIN_MAIL=voms.administrator@cnaf.infn.it

ORACLE_CONNECTION_STRING="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST = voms-db-02.cr.cnaf.infn.it)(PORT = 1521)))(CONNECT_DATA=(SERVICE_NAME = vomsdb2.cr.cnaf.infn.it)))"

VO_CERT_ORACLE_VOMS_PORT=15000
VO_CERT_ORACLE_VOMS_DB_USER=admin_25
VO_CERT_ORACLE_VOMS_DB_PASS=pwd

WMS

• Mandatory general variables
  • BDII_HOST
  • GROUPS_CONF
  • MYSQL_PASSWORD
  • SE_LIST
  • SITE_NAME
  • SITE_EMAIL
  • USERS_CONF
  • VOS
  • VO_<vo-name>_SW_DIR
  • VO_<vo-name>_VOMSES
  • VO_<vo-name>_VOMS_SERVERS
  • VO_<vo-name>_VOMS_CA_DN

• Mandatory service specific variables: they can be found in /opt/glite/yaim/examples/services/glite-wms:

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-wms.pre:

WN

• Mandatory general variables
  • BDII_HOST
  • MON_HOST (not needed anymore in gLite 3.2 WN)
  • SE_LIST
  • SITE_NAME
  • USERS_CONF
  • VOS
  • VO_<vo-name>_SW_DIR
  • VO_<vo-name>_VOMS_CA_DN (Mandatory for glite-yaim-core > 4.0.5-7)
  • VO_<vo-name>_VOMSES

• Optional service specific variables: they can be found in /opt/glite/yaim/examples/siteinfo/services/glite-wn:

Variable Name	Description	Value type	Version
GLITE_LOCAL_CUSTOMIZATION_DIR	This is an optional variable to define a scratch area for pool accounts via EDG_WL_SCRATCH. For more information please check http://glite.web.cern.ch/glite/packages/R3.0/deployment/glite-WN/3.0.15-3/glite-WN-3.0.15-3-update.html.	path	4.0.8-1

• Default service specific variables: they can be found in /opt/glite/yaim/defaults/glite-wn.post:

-- MariaALANDESPRADILLO - 29 Jul 2008