You are here: INFN-GRID Release Wiki » Documentation » Guides » INFNGRID YAIM configuration variables
INFNGRID YAIM configuration variables
MAIN NEWS from Update 53/54/55 - 23/09/2009
- New site-info.pre and .post variables:
- BDII_ARCHIVE_SIZE: It is the number of dumps of the database to keep for debugging purposes. Default is 0.
- BDII_BREATHE_TIME: It is the time in seconds between updates of the bdii. Default is 120.
- BDII_PASSWD: This is the password for the LDAP database used by the bdii. Default is $(mkpasswd -s 0).
- BDII_READ_TIMEOUT: It is the amount of time to wait until an information is assumed to have timed out. Default is 300.
- CONFIG_GRIDMAPDIR: It enables or disables the creation of the gridmap file. If set to yes, it creates it. If set to no, it doesn't create the gridmap file. Default is yes.
- 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. Default is 2h.
- TOMCAT_HOSTCERT_LOCATION: path of the tomcat host certificate. Default is /etc/grid-security/tomcat-cert.pem.
- TOMCAT_HOSTKEY_LOCATION: path of the tomcat host key. Default is /etc/grid-security/tomcat-key.pem.
- TOMCAT_USER: tomcat user. Default is tomcat.
MAIN NEWS from Update 44/45 - 25/05/2009
- New siteinfo variables:
- UNPRIVILEGED_MKGRIDMAP:
In case you want to create a grid-map file which only contains mappings to ordinary users. Values are 'yes' or 'no'. '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. This variable is defined in site-info.pre. Default is 'no'. You can redefine it in your site-info.def.
- GRIDFTP_CONNECTIONS_MAX:
Maximum number of simultaneous connections to the gridftp server. This variable is defined in site-info.pre. Default is '50'. You can redefine it in your site-info.def.
- BDII_LIST:
This variable already appeared in the previous yaim core release 4.0.5-7. However, due to a bug it was recommened not to use it. It's an optional variable to define a list of top level BDIIs to support the automatic failover in the GFAL clients. The syntax is my-bdii1.$MY_DOMAIN:port1[,my-bdii22.$MY_DOMAIN:port2[…]]. Be aware that lcg-infosites doesn't work with multiple BDIIs. So it's better you don't define this variable if you need to use lcg-infosites. However gfal, lcg_utils, lcg-info and glite-sd-query work fine with multiple BDIIs.
- 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 the 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'.
- CE_CAPABILITY and CE_OTHERDESCR:
These variables affect cream_CE and lcg_CE and that is why they are included in the example site-info.def. However, they are currently not used until some modifications in the information system configuration are applyed in cream and lcg CE. They will be properly announced by then. You can ignore them for the time being
General
In the following tables (on the list below click the profile you are interested in to expand the table) all the INFNGRID variables and some important gLite variables that can be configured in <your-site-info.def> are listed in alphabetically sorting (links to gLite variables are also listed):
- C = compulsory, if you are going to configure that type of node;
- O = optional.
For the other gLite variables please consider the official “site-info.def” information at ” YAIM 4 guide for sysadmins”.
Generic| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
BASE_SW_DIR | O | Directory exported for SGM (it will be mounted by WN on VO_SW_DIR, see below). Comment it if you have your own mounting tool. | 3.0.1-0 |
CE_INT_HOST | O | If PRIVATE_NETWORK=true, uncomment and write the internal FQDN hostname of CE. | 3.0.1-0 |
CE_LOGCPU | C | Total number of logical CPUs in the system (i.e. number of cores/hyperthreaded CPUs). | 4.0.3-0 |
CE_OS | C | OS type. Set using the output of the following command run on your WNs: # lsb_release -i | cut -f2 ScientificSL More details here: ” How to publish the OS name”. | 3.0.1-0 |
CE_OS_ARCH | C | OS architecture. Set using the output of the following command run on your WNs: # uname -m i686 More details here: ” How to publish my machine architecture”. | 3.0.1-0 |
CE_OS_RELEASE | C | OS release. Set using the output of the following command run on your WNs: # lsb_release -r | cut -f2 4.5 More details here: ” How to publish the OS name”. | 3.0.1-0 |
CE_OS_VERSION | C | OS version. Set using the output of the following command run on your WNs: # lsb_release -c | cut -f2 Beryllium More details here: ” How to publish the OS name”. | 3.0.1-0 |
CE_PHYSCPU | C | Total number of physical CPUs in the system (i.e. number of sockets). ATTENTION: if you have more than one CE and shared WNs set this variable to ” 0”. More details here: ” GIISQuery_Usage”. | 4.0.3-0 |
HOST_SW_DIR | O | Host exporting the directory for SGM (usually a CE or a SE). | 3.0.1-0 |
INT_NET | O | If PRIVATE_NETWORK=true, uncomment and write your internal network. | 3.0.1-0 |
INT_HOST_SW_DIR | O | If PRIVATE_NETWORK=true, uncomment and write the internal hostname of the host exporting the directory used to install the application software. | 3.0.1-0 |
MY_INT_DOMAIN | O | If PRIVATE_NETWORK=true, uncomment and write the internal domain name | 3.0.1-0 |
NTP_HOSTS_IP | C | Space separed list of the IP addresses of the NTP servers (preferably set a local ntp server and a public one, ex. pool.ntp.org). | 3.0.1-0 |
PRIVATE_NETWORK | O | Set PRIVATE_NETWORK=true to use WN on private network. | 3.0.1-0 |
Batch server| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
BATCH_LOG_DIR | C | Path for the batch-system log files: ”/var/spool/pbs” (for torque); ”/lsf_install_path/work/cluster_name/logdir” (for LSF). In case of separate batch-master (not on the same machine as the CE) PLEASE make sure that this directories are READABLE from the CEs | 3.0.1-0 |
BATCH_CONF_DIR | C | Only for LSF. Set path where lsf.conf file is located. | 3.0.1-0 |
DGAS services on CE (CE LCG, CE CREAM)| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
DGAS_ACCT_DIR | C | Path for the batch-system log files. - for torque/pbs: DGAS_ACCT_DIR=/var/spool/pbs/server_priv/accounting - for LSF: DGAS_ACCT_DIR=lsf_install_path/work/cluster_name/logdir | 4.0.8-3 |
DGAS_IGNORE_JOBS_LOGGED_BEFORE | O | Bound date on jobs backward processing. The backward processing doesn't consider jobs prior to that date. Use the format as in this example: DGAS_IGNORE_JOBS_LOGGED_BEFORE="2007-01-01"
Default value: | 4.0.2-9 |
DGAS_JOBS_TO_PROCESS | O | Specify the type of job which the CE has to process. ATTENTION: set ” all” on “the main CE” of the site (the one with the best hardware), ”grid” on the others. Default value: all | 4.0.2-9 |
DGAS_VO_TO_PROCESS | O | This parameter can be used to specify the list of VOs to publish. If the parameter is specified, the sensors (pushd) will forward to the Site HLR just records belonging to one of the specified VOs. Leave commented if you want to send records for ALL VOs Default value: parameter not specified | 4.0.12-3 |
DGAS_HLR_RESOURCE | C | Reference Resource HLR hostname. There is no need to specify the port as in the previous yaim versions (default value ”56568” will be set by yaim). | 4.0.2-9 |
DGAS_USE_CE_HOSTNAME | O | Only for LSF. Main CE of the site. ATTENTION: set this variable only in the case of site with a single LSF Batch Master (no need to set this variable in the Torque case) in which there are more than one CEs or local submission hosts (i.e. host from which you may submit jobs directly to the batch system.). In this case, DGAS_USE_CE_HOSTNAME parameter must be set to the same value for all hosts sharing the “lrms” and this value can be arbitrary chosen among these submitting hostnames (you may choose the best one). Otherwise leave it commented. For example: DGAS_USE_CE_HOSTNAME="my-ce.my-domain" | 4.0.2-9 |
DGAS_MAIN_POLL_INTERVAL | O | UR Box parse interval, that is if all jobs have been processed: seconds to wait before looking for new jobs in UR Box. default value “5” | 4.0.11-4 |
DGAS_JOB_PER_TIME_INTERVAL | O | Number of jobs to process at each processing step (several steps per mainPollInterval, depending on the number of jobs found in chocolateBox). default value “40” | 4.0.11-4 |
DGAS_TIME_INTERVAL | O | Time in seconds to sleep after each processing step (if there are still jobs to process, otherwise start a new mainPollInterval). default value “3” | 4.0.11-4 |
DGAS_QUEUE_POLL_INTERVAL | O | Garbage clean-up interval in seconds. default value “2” | 4.0.11-4 |
DGAS_SYSTEM_LOG_LEVEL | O | The “systemLogLevel” parameter defines the log verbosity from 0(no logging) to 9(maximum Verbosity) default value “7” | 4.0.11-4 |
DGAS_VO_TO_PROCESS | O | This parameter can be used to specify the list of VOs to publish. If the parameter is specified, the sensors (pushd) will forward to the Site HLR just records belonging to one of the specified VOs. Leave commented if you want to send records for ALL VOs. Syntax DGAS_VO_TO_PROCESS=“vo1;vo2;vo3…”, default value: parameter not specified | 4.0.11-4 |
AMGA BDII SiteConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
BDII_<nodetype>_URL | C | If you are configuring a 3.1 node change the port to 2170 and mds-vo-name to resource. For example: BDII_CE_URL="ldap://$CE_HOST:2170/mds-vo-name=resource,o=grid" | 3.0.1-0 |
CLOSE_SE_HOST | C | Set the close SE for the site. It is chosen between one of the site SEs. | >= 4.0.3-0 |
SITE_BDII_HOST | C | Host name of site BDII | >= 3.0.1-0 |
SITE_DESC | C | A long format name for your site | >= 4.0.4-0 |
SITE_SECURITY_EMAIL | C | Contact email for security | >= 4.0.4-0 |
SITE_OTHER_GRID | C | Grid to which your site belongs to, i.e. WLG or EGEE. Use: SITE_OTHER_GRID="EGEE" | 4.0.4-0 |
SITE_OTHER_EGEE_ROC | C | Agree within your ROC what the field should be. USE: SITE_OTHER_EGEE_ROC="Italy" | 4.0.4-0 |
BDII Top CE CREAMConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/glite-creamce
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
| ACCESS_BY_DOMAIN | C | By default the cream db is installed on localhost and accessible only from localhost. Setting ACCESS_BY_DOMAIN to true, you allow the cream db to be accessed from all computers in your domain. | >= 4.0.5-4 |
| BATCH_CONF_DIR | C | LSF settings: path where lsf.conf is located | >= 4.0.5-4 |
| BLAH_JOBID_PREFIX | C | This parameter sets the BLAH jobId prefix (it MUST be 6 chars long, begin with cr and terminate by '_'). It is important in case of more than one CE connecting to the same blparser. In this case, it is better that each CREAM_CE has its own prefix. The default value for this variable (as specified in opt/glite/yaim/defaults/glite-creamce.pre) is “cream_” | >= 4.0.5-4 |
| BLPARSER_HOST | C | to refer to the host where the Blah Log Parser is running or where the blparser is running (i.e. the variable xxx_BLPserver of blah.config). In this machine batch system logs must be accessible | >= 4.0.5-4 |
| BLP_PORT | C | to refer to the the port where Blah Log Parser is running (i.e. the variable xxx_BLPport of blah.config, GLITE_CE_BLPARSERxxx_PORT1 of blparser.conf) | >= 4.0.5-4 |
| CREAM_CE_STATE | C | This is the value to be published as GlueCEStateStatus instead of Production. The default value for this variable (as specified in opt/glite/yaim/defaults/glite-creamce.pre) is “Special” | >= 4.0.5-4 |
| CREAM_DB_USER | C | Database user to access cream database (different by root). Yaim will create this user and grant him the access rights | >= 4.0.5-4 |
| CEMON_HOST | O | Cream CE host name. In a more complex layout, the ce-monitor can be installed in a host different from the cream-ce host. In that case you need to put the right ce-monitor hostname in this variable. | >= 4.0.5-4 |
| CREAM_PORT | C | to refer to the parser listening cream port (i.e. the variable GLITE_CE_BLPARSERxxx_CREAMPORT1 of blparser.conf) | >= 4.0.5-4 |
| JOB_MANAGER | C | The name of the job manager used by the gatekeeper. For CREAM please define: pbs, lsf, sge or condor | >= 3.0.1-0 |
CE LCGConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/lcg-ce/opt/glite/yaim/examples/siteinfo/services/glite-mpi/opt/glite/yaim/examples/siteinfo/services/glite-mpi_ce
Please copy and edit those files in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
CE_RUNTIMEENV | C | Add the following tags to runtime environment: * If your site belongs to INFN write <CITY> in capitals (ex. PADOVA) otherwise <INSTITUTE>-<CITY> in capitals (ex. SNS-PISA) * Write the average value of SpecInt2000 and SpecFloat2000 for your WNs; please note that now a '_' is used as separator in place of '=' (see at http://grid-it.cnaf.infn.it/fileadmin/Certification/MetricHowTo.pdf): SI00MeanPerCPU_<your_value> SF00MeanPerCPU_<your_value> | >= 3.0.1-0 |
FTSConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/glite-ftm2
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
LB GRELCConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/ig-grelc
Please copy and edit that file in your <confdir>/services directory (have a look at ”INFNGRID YAIM configuration files”).
For any details please refer to the GRelC home-page.
HLRConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/ig-hlr
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
DGAS_HLR_ENABLE_URFORWARD | O | Enable the data forward to one or more second level HLRs. Default value: yes | 4.0.2-9 |
DGAS_HLR_DB_NAME | O | Set the name of the database for HLR service. Default value: hlr | 4.0.2-9 |
DGAS_HLR_DB_PASSWORD | C | Set the password to connect to the MySQL database server (with $DGAS_HLR_DB_USER user to $DGAS_HLR_DB_NAME database; not set by default). | 4.0.2-9 |
DGAS_HLR_DB_USER | O | Set the user for the MySQL database connection to $DGAS_HLR_DB_NAME database. Default value: dgas | 4.0.2-9 |
DGAS_HLR_TMP_DB_NAME | O | Set the name of the temporary database for HLR service. Default value: hlr_tmp | 4.0.2-9 |
You also find some variables related to R-GMA and also valid for MON profile. For any details please refer to this guide.
HYDRAConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/ig-hydra_mysql
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
Example 1: Three instances on the same server
HYDRA_INSTANCES="1 2 3" HYDRA_DBNAME_1=hydra_db_1 HYDRA_DBUSER_1=hydra1 HYDRA_DBPASSWORD_1=xxxx HYDRA_CREATE_1=/enmr.eu/Role=NULL/Capability=NULL HYDRA_ADMIN_1=/enmr.eu/Role=admin HYDRA_DBNAME_2=hydra_db_2 HYDRA_DBUSER_2=hydra2 HYDRA_DBPASSWORD_2=xxxx HYDRA_CREATE_2=/enmr.eu/Role=NULL/Capability=NULL HYDRA_ADMIN_2=/enmr.eu/Role=admin HYDRA_DBNAME_3=hydra_db_3 HYDRA_DBUSER_3=hydra3 HYDRA_DBPASSWORD_3=xxxx HYDRA_CREATE_3=/enmr.eu/Role=NULL/Capability=NULL HYDRA_ADMIN_3=/enmr.eu/Role=admin
Example 2: Single instance on a server, into a system of three separated HYDRA servers
HYDRA_INSTANCES="1" HYDRA_DBNAME_1=hydra_db_1 HYDRA_DBUSER_1=hydra1 HYDRA_DBPASSWORD_1=xxxx HYDRA_CREATE_1=/enmr.eu/Role=NULL/Capability=NULL HYDRA_ADMIN_1=/enmr.eu/Role=admin HYDRA_PEERS="2 3" HYDRA_CREATE_2=/enmr.eu/Role=NULL/Capability=NULL HYDRA_ID_2=1 HYDRA_HOST_2=hydra.host.fqn HYDRA_CREATE_3=/enmr.eu/Role=NULL/Capability=NULL HYDRA_ID_3=1 HYDRA_HOST_3=hydra.host.fqn2
The section “HYDRA_PEERS” contains the information about the servers installed on remote machines, that have to work with the server you're installing. Please note that HYDRA_ID is the remote hydra server “instance id” specified into its site-info configuration file. If you have only one installation for every single machine, most probably the HYDRA_IDs are all ”=1”. Ask remote servers' site admins.
After the Hydra installation and configuration, you'll be able to get service information by a LDAP query vs. <hydra_hostname>:2170. So you'll need to register it into your site-BDII. All the Hydra services must be found into a top-BDII to work together. </box>
LFC| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
LFC_READONLY | O | Set this var to “yes” if your LFC server is a replica of a “central” one, and has to be read_only for users. Default value: no | 4.0.4-2 |
MyProxy SE dCacheConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/glite-dcache
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
Please pay attention on the configuration of a dCache node - follow the instructions present at:
SE DPMConfiguration file
Specific variables are in (copy only the one you need):
/opt/glite/yaim/examples/siteinfo/services/glite-se_dpm_disk/opt/glite/yaim/examples/siteinfo/services/glite-se_dpm_mysql/opt/glite/yaim/examples/siteinfo/services/glite-se_dpm_oracle
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
SE StoRM BackendConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/ig-se_storm_backend
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
| Variable name | Type | Descpription | >= ig-yaim-storm version |
|---|---|---|---|
STORM_ACLMODE | O | ACL enforcing mechanism (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_ACLMODE variable. Available values: [aot|jit] (use aot for WLCG experiments) Default value: aot | 4.0.4-0 |
STORM_AUTH | O | Authorization mechanism (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_AUTH variable. Available values: [permit-all|deny-all|<filename>] Default value: permit-all | 4.0.7-0 |
 STORM_BACKEND_HOST (was STORM_HOST) | C | In ig-site-info.def template. Host name of the StoRM Backend server. | 4.0.9-0 |
STORM_CERT_DIR (was STORM_HOSTCERT and STORM_HOSTKEY) | O | Host certificate directory for StoRM Backend service. Default value: /etc/grid-security/${STORM_USER} | 4.0.9-0 |
STORM_CKSUM_ALGORITHM | O | Algorithm used by checksum agents. Available values: [Adler32|CRC32|MD2|MD5|SHA-1|SHA-256|SHA-384|SHA-512] Default value: Adler32 | 4.0.9-0 |
STORM_CKSUM_SERVICE_LIST | O | Checksum agents list. ATTENTION: this variable define a list of three comma-separated values: hostname,status_port,service_port e.g.: STORM_CKSUM_SERVICE_LIST="host1,status_port1,service_port1 host2,status_port2,service_port2"
Default value: | 4.0.9-0 |
STORM_CKSUM_SUPPORT | O | Enable the support to checksum agents. Available values: [true|false] Default value: false | 4.0.9-0 |
STORM_DEFAULT_ROOT | C | In ig-site-info.def template. Default directory for Storage Areas. | 4.0.2-9 |
STORM_DB_HOST | O | Host for database connection. Default value: $STORM_BACKEND_HOST | 4.0.2-9 |
STORM_DB_PWD | C | Password for database connection. | 4.0.2-9 |
STORM_DB_USER | O | User for database connection. Default value: storm | 4.0.2-9 |
STORM_FRONTEND_HOST_LIST | O | StoRM Frontend service host list: SRM endpoints can be more than one virtual host different from STORM_BACKEND_HOST (i.e. dynamic DNS for multiple StoRM Frontends). Default value: $STORM_BACKEND_HOST | 4.0.2-9 |
STORM_FRONTEND_PATH | O | StoRM Frontend service path. Default value: /srm/managerv2 | 4.0.2-9 |
STORM_FRONTEND_PORT (was STORM_PORT) | O | StoRM Frontend service port. Default value: 8444 | 4.0.2-9 |
STORM_FRONTEND_PUBLIC_HOST (was STORM_ENDPOINT) | O | StoRM Frontend service public host. Default value: $STORM_BACKEND_HOST | 4.0.2-9 |
STORM_FSTYPE | O | File System Type (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_FSTYPE variable. Available values: [posixfs|xfs|gpfs] Default value: posixfs | 4.0.4-0 |
STORM_GRIDFTP_POOL_LIST | O | GRIDFTP servers pool list (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_GRIDFTP_POOL_LIST variable. ATTENTION: this variable define a lsit of pair values comma-separated: hostname,weight, e.g.: STORM_GRIDFTP_POOL_LIST="host1,weight1 host2,weight2 host3,weight3"
Weight has 0-100 range; if not specified, weight will be 100. | 4.0.7-0 |
STORM_GRIDFTP_POOL_STRATEGY | O | Load balancing strategy for GRIDFTP servers pool (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_GRIDFTP_POOL_STRATEGY variable. Available values: [round-robin|random|weight|metric-1|metric-2] Default value: round-robin | 4.0.7-0 |
STORM_INFO_FILE_SUPPORT STORM_INFO_GRIDFTP_SUPPORT STORM_INFO_RFIO_SUPPORT STORM_INFO_ROOT_SUPPORT | O | If set to false, the following variables prevent the corresponding protocol to be published by the StoRM gip. Available values: [true|false] Default value: true | 4.0.2-9 |
STORM_INFO_OVERWRITE | O | This parameter tells YAIM to overwrite static-file-StoRM.ldif configuration file. Available values: [true|false] Default value: true | 4.0.2-9 |
STORM_NAMESPACE_OVERWRITE | O | This parameter tells YAIM to overwrite namespace.xml configuration file. Available values: [true|false] Default value: true | 4.0.2-9 |
STORM_PROXY_HOME | O | Directory used to exchange proxies. Default value: /opt/storm/backend/tmp | 4.0.2-9 |
STORM_RFIO_HOST | O | Rfio server (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_RFIO_HOST variable. Default value: $STORM_BACKEND_HOST | 4.0.9-0 |
STORM_ROOT_HOST | O | Root server (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_ROOT_HOST variable. Default value: $STORM_BACKEND_HOST | 4.0.9-0 |
STORM_SIZE_LIMIT | O | Limit Maximum available space on the Storage Area (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_SIZE_LIMIT variable. Available values: [true|false] Default value: true | 4.0.7-0 |
STORM_STORAGEAREA_LIST | O | List of supported Storage Areas. Usually at least one Storage Area for each VO specified in $VOS should be created. Default value: $VOS | 4.0.2-9 |
STORM_STORAGECLASS | O | Storage Class type (default value for all Storage Areas). Note: you may change the settings for each SA acting on $STORM_<SA>_STORAGECLASS variable. Available values: [T0D1|T1D0|T1D1] - No default value. | 4.0.9-0 |
STORM_SURL_ENDPOINT_LIST | O | StoRM SURL endpoint list. Default values: srm://${STORM_FRONTEND_PUBLIC_HOST}:${STORM_FRONTEND_PORT}${STORM_FRONTEND_PATH} | 4.0.9-0 |
STORM_USER | O | Service user. Default value: storm | 4.0.2-9 |
Then, for each <SA> “Storage Area” listed in STORM_STORAGEAREA_LIST variable you have to edit the following compulsory variables:
NOTE
<SA> has to be written in capital letters as in the other <site-info.def> variables otherwise default values will be used!
ATTENTION: for the DNS-like names (using special characters as ”.” (dot), ”-” (minus)) you have to remove the ”.”. ”-”: e.g. for STORM_STORAGEAREA_LIST=“enmr.eu” <SA> should be ENMREU like:
STORM_ENMREU_VONAME=enmr.eu
| Variable name | Type | Descpription | >= ig-yaim-storm version |
|---|---|---|---|
STORM_<SA>_VONAME | C | Name of the VO that will use the Storage Area (use the complete name, e.g. ”lights.infn.it”). | 4.0.2-9 |
and eventually the following optional variables:
| Variable name | Type | Descpription | >= ig-yaim-storm version |
|---|---|---|---|
STORM_<SA>_ACCESSPOINT | O | Path exposed by the SRM into the SURL. Default value: /<sa> | 4.0.2-9 |
STORM_<SA>_ACLMODE | O | See STORM_ACLMODE definition. Default value: $STORM_ACLMODE | 4.0.2-9 |
STORM_<SA>_AUTH | O | See STORM_AUTH definition. Default value: $STORM_AUTH | 4.0.7-0 |
STORM_<SA>_DEFAULT_ACL_LIST | O | A list of ACL entries that specifies a set of local groups with correspondig permissions (R,W,RW) using the following syntax: groupname1:permissions1 [groupname2:permissions2 [...]] | 4.0.7-0 |
STORM_<SA>_FILE_SUPPORT STORM_<SA>_GRIDFTP_SUPPORT STORM_<SA>_RFIO_SUPPORT STORM_<SA>_ROOT_SUPPORT | O | Enable the corresponding protocol. Default value: $STORM_INFO_<PROTOCOL>_SUPPORT | 4.0.2-9 |
STORM_<SA>_FSTYPE | O | See STORM_<SA>_FSTYPE definition. Default value: $STORM_FSTYPE | 4.0.2-9 |
STORM_<SA>_GRIDFTP_POOL_LIST | O | See STORM_GRIDFTP_POOL_LIST definition. Default value: $STORM_GRIDFTP_POOL_LIST | 4.0.7-0 |
STORM_<SA>_GRIDFTP_POOL_STRATEGY | O | See STORM_GRIDFTP_POOL_STRATEGY definition. Default value: $STORM_GRIDFTP_POOL_STRATEGY | 4.0.7-0 |
STORM_<SA>_QUOTA | O | Enables the quota management for the Storage Area and it works only on GPFS filesystem. Available values: [true|false] Default value: false | 4.0.2-9 |
STORM_<SA>_QUOTA_DEVICE | O | GPFS device on which the quota is enabled. It is mandatory if STORM_<SA>_QUOTA variable is set. No default value. | 4.0.9-0 |
STORM_<SA>_QUOTA_USER STORM_<SA>_QUOTA_GROUP STORM_<SA>_QUOTA_FILESET | O | GPFS quota scope. Only one of the following three will be used (the first one with the highest priority in this order: USER, then GROUP, then FILESET). No default value. | 4.0.9-0 |
STORM_<SA>_RFIO_HOST | O | See STORM_RFIO_HOST definition. Default value: $STORM_RFIO_HOST | 4.0.9-0 |
STORM_<SA>_ROOT | O | Physical storage path for the VO. Default value: $STORM_DEFAULT_ROOT/<sa> | 4.0.2-9 |
STORM_<SA>_ROOT_HOST | O | See STORM_ROOT_HOST definition. Default value: $STORM_ROOT_HOST | 4.0.9-0 |
STORM_<SA>_SIZE_LIMIT | O | See STORM_SIZE_LIMIT definition. Default value: $STORM_SIZE_LIMIT | 4.0.7-0 |
STORM_<SA>_STORAGECLASS | O | See STORM_STORAGECLASS definition. Available values: [T0D1|T1D0|T1D1|<null>] No default value. | 4.0.2-9 |
STORM_<SA>_TOKEN | O | Storage Area token, e.g: LHCb_RAW, INFNGRID_DISK, etc. No default value. | 4.0.2-9 |
SE StoRM FrontendConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/ig-se_storm_frontend
Please copy and edit that file in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
| Variable name | Type | Descpription | >= ig-yaim-storm version |
|---|---|---|---|
STORM_BACKEND_HOST (was STORM_HOST) | C | In ig-site-info.def template. Host name of the StoRM Backend server. | 4.0.9-0 |
STORM_CERT_DIR (was STORM_HOSTCERT and STORM_HOSTKEY) | O | Host certificate directory for StoRM Frontend service. Default value: /etc/grid-security/${STORM_USER} | 4.0.9-0 |
STORM_DB_HOST | O | Host for database connection. Default value: $STORM_BACKEND_HOST | 4.0.2-9 |
STORM_DB_PWD | C | Password for database connection. | 4.0.2-9 |
STORM_DB_USER | O | User for database connection. Default value: storm | 4.0.2-9 |
STORM_FE_BE_XMLRPC_HOST | O | StoRM Backend hostname. Default value: localhost | 4.0.7-0 |
STORM_FE_BE_XMLRPC_PATH | O | StoRM Backend XMLRPC server path. Default value: /RPC2 | 4.0.7-0 |
STORM_FE_BE_XMLRPC_PORT | O | StoRM Backend XMLRPC server port. Default value: 8080 | 4.0.7-0 |
STORM_FE_DISABLE_MAPPING | O | Disable the check in gridmapfile for client DN. Available values: [true|false] Default value: false | 4.0.7-0 |
STORM_FE_DISABLE_VOMSCHECK | O | Disable the check in gridmapfile for client VOMS attributes. Available values: [true|false] Default value: false | 4.0.7-0 |
STORM_FE_GSOAP_MAXPENDING | O | Max number of request pending in the GSOAP queue. Default value: 2000 | 4.0.7-0 |
STORM_FE_LOG_LEVEL | O | StoRM Frontend log level. Available values: [KNOWN|ERROR|WARNING|INFO|DEBUG|DEBUG2] Default value: INFO | 4.0.7-0 |
STORM_FE_THREADS_MAXPENDING | O | Max number of request pending in the Threads queue. Default value: 200 | 4.0.7-0 |
STORM_FE_THREADS_NUMBER | O | Max number of threads to manage user's requests. Default value: 50 | 4.0.7-0 |
STORM_FE_WSDL | O | WSDL to be returned to a GET request. Default value: /opt/storm/frontend/wsdl/srm.v2.2.wsdl | 4.0.7-0 |
STORM_FRONTEND_OVERWRITE | O | This parameter tells YAIM to overwrite storm-frondend.conf configuration file. Available values: [true|false] Default value: true | 4.0.2-9 |
STORM_PROXY_HOME | O | Directory used to exchange proxies. Default value: /opt/storm/backend/tmp | 4.0.7-0 |
STORM_USER | O | User on which StoRM service will run. Default value: storm | 4.0.2-9 |
UI VOBOXConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/glite-vobox
Please copy and edit those files in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
WMSConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/glite-wms
Please copy and edit those files in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
WNConfiguration file
Specific variables are in:
/opt/glite/yaim/examples/siteinfo/services/glite-mpi/opt/glite/yaim/examples/siteinfo/services/glite-mpi_wn
Please copy and edit those files in your <confdir>/services directory (have a look to ”INFNGRID YAIM configuration files”).
| Variable name | Type | Descpription | >= ig-yaim version |
|---|---|---|---|
GRIDICE_HIDE_USER_DN | C | Publish user certificate subject. | 3.0.1-0 |
GRIDICE_MON_WN | C | Enable monitoring on WN of generic processes/daemons using GridICE. | 3.0.1-0 |
doc/guides/site-info-variables.txt · Last modified: 2010/09/08 12:12 by caiftimiei
