Tags:
,
view all tags
%TOC% ---+ INFNGRID Installation and Configuration Guide for gLite 3.2 SL5 x86_64 This document is a complete guide for the installation and the configuration of INFNGRID profiles aligned with gLite middleware version 3.2 on SL5 (or RHEL5 clones) for x86_64 architecture (no i386 profiles have been deployed up to now). Currently only few profiles have been ported to *SL5 x86_64* and integrated in INFNGRID release. At the following link you can find the current status of gLite and INFNGRID porting: * [[https://twiki.cern.ch/twiki/bin/view/EGEE/SL5Planning][gLite Node Tracker]] * [[ig-node-tracker][INFNGRID Node Traker]] If you find errors in this document please open a ticket to the "Release & Documentation" group using the [[https://ticketing.cnaf.infn.it/][INFNGRID trouble ticketing system]]. *Released profiles:* *IMPORTANT NOTE:* Please be aware that the profile ig_GRIDFTP is obsoleted by the ig_SE_storm_gridftp, and an updgrade is not possible, only fresh installations of the ig_SE_storm_gridftp Here below an updated lists of currently deployed profiles with related metapackage and nodetype names: | *Profiles* | *INSTALLATION Metapackages* | *CONFIGURATION Nodetypes* | *Release date* | *Required in a grid site?* | | *ARGUS* | ''ig_ARGUS'' | ''ig_ARGUS_server'' <BR/> or <BR/> ''ARGUS_server''| <fc green>26/02/2010</fc> | **NO** | | *BDII Site* | ''ig_BDII_site'' | ''ig_BDII_site'' | <fc green>04.08.2010</fc> | **YES** | | *BDII Top* | ''ig_BDII_top'' | ''ig_BDII_top'' | <fc green>05/10/2010</fc> | **NO** | | *CREAM CE* | ''ig_CREAM'' <BR/> ''ig_CREAM_LSF'' <BR/> ''ig_CREAM_torque'' | ''ig_CREAM'' <BR/> ''ig_CREAM_LSF'' <BR/> ''ig_CREAM_torque'' | <fc green>09/02/2010</fc> | **YES** | | *FTA_oracle* | ''ig_FTA_oracle'' | ''ig_FTA_oracle'' | <fc green>21/07/2010</fc> | **NO** | | *FTM** | ''ig_FTM'' | ''ig_FTM'' | <fc green>21/07/2010</fc> | **NO** | | *FTS_oracle* | ''ig_FTS_oracle'' | ''ig_FTS_oracle'' | <fc green>21/07/2010</fc> | **NO** | | *GLEXEC_wn* | ''ig_GLEXEC_wn'' | ''ig_GLEXEC_wn'' | <fc green>18/12/2009 </fc> | **NO** | | *HLR* | ''ig_HLR'' | ''ig_HLR'' | <fc red>Not released</fc> | **NO** | | *LB* | ''ig_LB'' | ''ig_LB'' | <fc green>28/04/2010</fc> | **NO** | | *LFC* | ''ig_LFC_mysql'' <BR/> ''ig_LFC_oracle'' | ''ig_LFC_mysql'' <BR/> ''ig_LFC_oracle'' | <fc green>22/10/2009 <BR/> 08/02/2010</fc> | **NO** | | *SGE_utils* | ''ig_SGE_utils'' | ''ig_SGE_utils'' | <fc green>03/05/2010 </fc> | **NO** | | *SE dCache* | ''ig_SE_dcache_info'' <BR/> ''ig_SE_dcache_nameserver_chimera'' <BR/> ''ig_SE_dcache_pool'' <BR/> ''ig_SE_dcache_srm'' | ''ig_SE_dcache_info'' <BR/> ''ig_SE_dcache_nameserver_chimera'' <BR/> ''ig_SE_dcache_pool'' <BR/> ''ig_SE_dcache_srm''| <fc green>10/06/2011</fc> | **NO** | | *SE DPM* | ''ig_SE_dpm_mysql' '<BR/> ''ig_SE_dpm_disk'' | ''ig_SE_dpm_mysql'' <BR/> ''ig_SE_dpm_disk''| <fc green> 22/10/2009</fc> | **NO** | | *SE STORM* | ''ig_SE_storm_backend'' <BR/> ''ig_SE_storm_frontend'' <BR/> ''ig_SE_storm_checksum''<BR/> ''ig_SE_storm_gridftp'' | ''ig_SE_storm_backend'' <BR/> ''ig_SE_storm_frontend'' <BR/> ''ig_SE_storm_checksum'' <BR/> ''ig_SE_storm_gridftp'' | <fc green>23/03/2011</fc> | **NO** | | *UI* | ''ig_UI'' <BR/> ''ig_UI_noafs'' | ''ig_UI'' <BR/> ''ig_UI_noafs'' | <fc green>27/07/2009</fc> | **NO** <BR/> but recommended | | *VOBOX* | ''ig_VOBOX'' | ''ig_VOBOX'' | <fc green>22/10/2009 </fc> | **NO** | | *VOMS_mysql* | ''ig_VOMS_mysql'' | ''ig_VOMS_mysql'' | <fc green>03/05/2010 </fc> | **NO** | | *VOMS_oracle* | ''ig_VOMS_oracle'' | ''ig_VOMS_oracle'' | <fc green>18/08/2010 </fc> | **NO** | | *WN* | ''ig_WN'' <BR/> ''ig_WN_noafs'' <BR/> ''ig_WN_LSF'' <BR/> ''ig_WN_LSF_noafs'' <BR/> ''ig_WN_torque'' <BR/> ''ig_WN_torque_noafs'' | ''ig_WN'' <BR/> ''ig_WN_noafs'' <BR/> ''ig_WN_LSF'' <BR/> ''ig_WN_LSF_noafs'' <BR/> ''ig_WN_torque'' <BR/> ''ig_WN_torque_noafs'' | <fc green>24/07/2009</fc> | **YES** | Please keep in mind the difference between the following three concepts because of their different scopes and uses: * *profile* => we use this word to __//generically//__ call a service * *metapackage* => we use this word during __//installation//__ phase * *nodetype* => we use this word during __//configuration//__ phase *Documentation references:* Please also refer to these gLite official guides: * [[https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide320][Generic Installation and Configuration Guide for gLite 3.2]] * [[https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400][YAIM 4 Guide for Sysadmins]] * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables][YAIM Configuration Variables]] * [[https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400#Known_issues][YAIM 4 Known Issues]] ---++ *Installation* ---+++ OS installation Install SL5 using [[http://linuxsoft.cern.ch/scientific/5x/][ SL5.X repository (CERN mirror)]] or one of the supported <acronym title="Operating System">OS</acronym> (RHEL5 clones). You may find information on official repositories at [http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:tips:repos][Repositories for APT and YUM]] <br /> If you want to set up a local installation server please refer to [[http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:tips:mrepo][Mrepo Quick Guide]] *NOTE*: Please check if <em> =NTP= </em>, <em> =cron= </em> and <em> =logrotate= </em> are installed, otherwise install them! ---++++ Check the FQDN hostname Ensure that the hostnames of your machines are correctly set. Run the command: <pre> hostname -f</pre> It should print the fully qualified domain name (e.g. =prod-ce.mydomain.it=). Correct your network configuration if it prints only the hostname without the domain. If you are installing WN on private network the command must return the external FQDN for the CE and the SE (e.g. =prod-ce.mydomain.it=) and the internal FQDN for the WNs (e.g. =node001.myintdomain=). ---+++ Repository Settings To have more details to the repository have a look to the this link [[http://wiki.italiangrid.org/twiki/bin/view/IGIRelease/RepositoriesSpecifications][Repository Specifications]] With standard installation of SL5 it's possible that you have the EPEL repository enabled. Please disable it: <pre># mv /etc/yum.repos.d/epel.repo /etc/yum.repos.d/epel.repo.disabled </pre> otherwise you'll get the following error: <pre>Missing Dependency: libcares.so.0()(64bit) is needed by package glite-security-gss-2.0.0-3.sl5.x86_64 (glite-generic_sl5_x86_64_release) </pre> because of the presence of newer version of c-ares (1.4.0-1.el5). The middleware needs the 1.3.0-4.sl5 ! Remeber to enabled the dag.repo : With standard installation of SL5 it's possible that you have the DAG repository. Please check if it is enabled, if no please enabled it: cat /etc/yum.repos.d/dag.repo .... enabled=1 .... ---++++ Common repositories Each profile needs a set of common repositories: | *Common repositories *x86_64** | | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/dag.repo][dag.repo]] | | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/ig.repo][ig.repo]] | | [[http://repo-pd.italiangrid.it/mrepo/repos/egi-trustanchors.repo][egi-trustanchors.repo]] | In order to have a working IGI service you have to download also the gLite repo files. In the table bellow you'll find the match from metapackages to profiles. ---++++ Profile-specific repositories Furthermore each profile needs a set of repositories that contain the profile-related middleware. Look at the table below to know what specific repositories your profile needs: | *Metapackages* | *Profile-specific repositories *x86_64** | | ig_ARGUS | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-argus.repo][glite-argus.repo]] | | ig_BDII_top | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-bdii_top.repo][glite-bdii_top.repo]] | | ig_BDII_site | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-bdii_site.repo][glite-bdii_site.repo]] | | ig_CREAM <br /> ig_CREAM_LSF | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-cream.repo][glite-cream.repo]] | | ig_CREAM_torque | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-cream_torque.repo][glite-cream_torque.repo]] | | ig_FTA_oracle | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-fta_oracle.repo][glite-fta_oracle.repo]] | | ig_FTM | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-ftm.repo][glite-ftm.repo]] | | ig_FTS_oracle | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-fts_oracle.repo][glite-fts_oracle.repo]] | | ig_GLEXEC_wn | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-glexec.repo][glite-glexec.repo]] | | ig_HLR | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-generic.repo][glite-generic.repo]] | | ig_LB | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-lb.repo][glite-lb.repo]] | | ig_LFC_mysql | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-lfc_mysql.repo][glite-lfc_mysql.repo]] | | ig_SE_dpm_mysql | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dpm_mysql.repo][glite-se_dpm_mysql.repo]] | | ig_SE_dcache_info | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dcache_info.repo][glite-se_dcache_info.repo]] | | ig_SE_dcache_nameserver_chimera | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dcache_nameserver.repo][glite-se_dcache_nameserver.repo]] | | ig_SE_dcache_pool | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dcache_pool.repo][glite-se_dcache_pool.repo]] | | ig_SE_dcache_srm | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dcache_srm.repo][glite-se_dcache_srm.repo]] | | ig_SE_storm_backend <br /> ig_SE_storm_frontend <br /> ig_SE_storm_checksum | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/ig-storm.repo][ig-storm.repo]] | | ig_SE_storm_gridftp | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/ig-storm_gridftp.repo][ig-storm_gridftp.repo]] | | ig_UI <br /> ig_UI_noafs | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-ui.repo][glite-ui.repo]] | | ig_VOBOX | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-vobox.repo][glite-vobox.repo]] | | ig_VOMS_mysql | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-voms_mysql.repo][glite-voms_mysql.repo]] | | ig_VOMS_oracle | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-voms_oracle.repo][glite-voms_oracle.repo]] | | ig_WN, ig_WN_noafs<strong> <br /> </strong>ig_WN_LSF, ig_WN_LSF_noafs | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-wn.repo][glite-wn.repo]] | | ig_WN_torque, ig_WN_torque_noafs | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-wn_torque.repo][glite-wn_torque.repo]] | Then update your host: <pre>yum clean all </pre> ---+++ CAa installation: Install CAs on ALL profiles: <pre>yum install ca-policy-egi-core </pre> ---+++ Metapackage installation Please consider that x86_64 WN profiles has to be installed using the “groupinstall” yum command as follows: <pre> yum groupinstall <WN_profile> </pre> where <WN_profile> could be one of: ig_WN, ig_WN_noafs, ig_WN_torque, ig_WN_torque_noafs, ig_WN_LSF, ig_WN_LSF_noafs or <pre> yum groupinstall <UI_profile> </pre> where <UI_profile> could be one of: ig_UI, ig_UI_noafs If you are installing any othere profiles use: <pre> yum install <metapackage> </pre> Where =<metapackage>= is one of those reported on the table above ( _Metapackages_ column). *IMPORTANT NOTE:* When you are installing ig_CREAM or ig_CREAM_LSF or ig_CREAM_torque adding an exclude line to the .repo file, e.g. in /etc/yum.repos.d/slc5-updates.repo or /etc/yum.repos.d/sl5-security.repo <pre> exclude=c-ares </pre> ---++++Special cases ---+++++CE and Batch Server configuration (access to log files) It doesn't matter what kind of deployment you have, batch-system master on a different machine than the CE (CREAM, TORQUE or LSF) or on the same one, you have to be sure that you provide *access* to the *batch system log files*: You must set up a mechanism to ''transfer'' accounting logs to the CE: * through NFS (don't forget to set $BATCH_LOG_DIR and $DGAS_ACCT_DIR in <your-site-info.def> configuration file) * through a daily cron job to the directory defined in $BATCH_LOG_DIR and $DGAS_ACCT_DIR in <your-site-info.def> configuration file ---+++++CREAM_torque (multiple CEs and single Batch Server) This configuration requires particular attention both during the metapackage installation and during the nodetype configuration. Install the first CE (that will act also as Batch Server) following the usual procedure: <pre> yum install ig_CREAM_torque </pre> Install the other secondary CEs without batch server software as follows: <pre> yum install ig_CREAM glite-TORQUE_utils </pre> ---+++++Standalone TORQUE_server You should use the following .repo files, [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-torque_server.repo][glite-torque_server.repo]] & [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-torque_utils.repo][glite-torque_utils.repo]] <pre> yum install glite-TORQUE_server glite-TORQUE_utils </pre> for the CEs (creamCEs), add the [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-torque_utils.repo][glite-torque_utils.repo]] file and: <pre> yum install ig_CREAM glite-TORQUE_utils </pre> Please pay attention also to the configuration for this special case ---+++ Batch system installation (only for WN) LSF server/client installation must be done **manually**, whereas Torque server/client installation is included in the metapackage. ---++ *Configuration* ---+++ Configuration files ---++++ INFNGRID YAIM configuration files YAIM configuration files should be stored in a _directory structure_. All the involved files *HAVE* to be under the same folder =<confdir>=, in a safe place, which *is not world readable*. This directory should contain: | *File* | *Scope* | *Details* | | =<your-site-info.def>= | *whole-site* | List of configuration variables in the format of key-value pairs. <br /> It's a *mandatory* file. <br /> It's a parameter passed to the =ig_yaim= command. <br /> *IMPORTANT*: You should always check if your =<your-site-info.def>= is up-to-date comparing with the last =/opt/glite/yaim/examples/siteinfo/ig-site-info.def= template deployed with =ig-yaim= and get the differences you find. <br /> For example you may use =vimdiff=: <pre>vimdiff /opt/glite/yaim/examples/siteinfo/ig-site-info.def <confdir>/<your-site-info.def></pre> | | =<your-wn-list.conf>= | *whole-site* | Worker nodes list in the format of =hostname.domainname= per row. <br /> It's a *mandatory* file. <br /> It's defined by =WN_LIST= variable in =<your-site-info.def>=. | | =<your-users.conf>= | *whole-site* | Pool account user mapping. <br /> It's a *mandatory* file. <br /> It's defined by =USERS_CONF= variable in =<your-site-info.def>=. <br /> *IMPORTANT*: You may create =<your-users.conf>= starting from the =/opt/glite/yaim/examples/ig-users.conf= template deployed with =ig-yaim=, but probably you have to fill it on the base of your site policy on uids/guis. We suggest to proceed as explained here: _”<a href="http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:use_cases:users" title="doc:use_cases:users">Whole site: How to create local users.conf and configure users</a>”_. | | =<your-groups.conf>= | *whole-site* | VOMS group mapping. <br /> It's a *mandatory* file. <br /> It's defined by =GROUPS_CONF= variable in =<your-site-info.def>=. <br /> *IMPORTANT*: You may create =<your-groups.conf>= starting from the =/opt/glite/yaim/examples/ig-groups.conf= template deployed with =ig-yaim=. | ---++++ Additional files Furthermore the configuration folder can contain: | *Directory* | *Scope* | *Details* || | =services/= | *service-specific* | It contains a file per nodetype with the name format: =ig-node-type=. <br /> The file contains a list of configuration variables specific to that nodetype.<br /> Each yaim module distributes a configuration file in =/opt/glite/yaim/examples/siteinfo/services/[ig or glite]-node-type. <br /> It's a *mandatory* directory if required by the profile and *you should copy it* under the same directory where <your-site-info.def> is. | | | =nodes/= | *host-specific* | It contains a file per host with the name format: =hostname.domainname=. <br /> The file contains host specific variables that are different from one host to another in a certain site. <br /> It's an *optional* directory. || | =vo.d/= | *VO-specific* | It contains a file per VO with the name format: =vo_name=, but most of VO settings are still placed in =ig-site-info.def= template. For example, for ”<code>lights.infn.it</code>”: <pre># cat vo.d/lights.infn.it<br />SW_DIR=$VO_SW_DIR/lights<br />DEFAULT_SE=$SE_HOST<br />VOMS_SERVERS="vomss://voms2.cnaf.infn.it:8443/voms/lights.infn.it?/lights.infn.it"<br />VOMSES="lights.infn.it voms2.cnaf.infn.it 15013 /C=IT/O=INFN/OU=Host/L=CNAF/CN=voms2.cnaf.infn.it lights.infn.it"</pre> <p>It's an *optional* directory for “normal” VOs (like atlas, alice, babar), *mandatory* only for “fqdn-like” VOs. In case you support such VOs *you should copy* the structure vo.d/<vo.specific.file> under the same directory where <your-site-info.def> is.</p> || | =group.d/= | *VO-specific* | It contains a file per VO with the name format: =groups-<vo_name>.conf=. <br /> The file contains VO specific groups and it replaces the former =<your-groups.conf>= file where all the VO groups were specified all together. <br /> It's an *optional* directory. || The optional folders are created to allow system administrators to organise their configurations in a more structured way.” *IMPORTANT NOTE:* <br /> If your site has the intention to support more VOs than the default ones, you should have a look at [[http://wiki.italiangrid.it/twiki/bin/view/IGIRelease/EnableVo][Whole site: How to enable a VO]], specially for the *enmr.eu* VO, once the configuration finished you should follow "[[http://wiki.italiangrid.it/twiki/bin/view/IGIRelease/EnableVo#Extra_configuration][extra_configuration]]". ---++++Default files Variables that contain a meaningful default value are distributed under ''/opt/glite/yaim/defaults/'' directory and that don't need to be changed unless you are an advanced user and you know what you are doing. The files are: * ''ig-site-info.pre''; * ''ig-site-info.post''; * ''<node-type>.pre'', ''glite-<node-type>.pre'', ''ig-<node-type>.pre''; * ''<node-type>.post'', ''glite-<node-type>.post'', ''ig-<node-type>.post''. In case you really need to change these variables, you don't need to modify the value in these files if you don't want to edit them. You can just add the same variable in site-info.def since this will overwrite the variables declared in these files. See the configuration flow in YAIM in the next section. ---++++Configuration flow This is the order in which the different configuration files are sourced (''<confdir>'' refers to the path of the configuration folder which is the path of ''<your-site-info.def>''): 1. defaults ''.pre'' files in ''/opt/glite/yaim/defaults/''; 1. ''<confdir>/<your-site-info.def>''; 1. service-specific files in ''<confdir>/services/''; 1. defaults ''.post'' files in ''/opt/glite/yaim/defaults/''; 1. node-specific files in ''<confdir>/nodes/''; 1. VO-specific files in ''<confdir>/vo.d/''; 1. function files in ''/opt/glite/yaim/node-info.d/''; 1. VO-specific group settings in ''<confdir>/group.d/*''. ---+++ Configuration variabiles ---++++ General In the documentation you could find 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 "[[https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400#site_info_def][YAIM 4 guide for sysadmins]]". ---+++++Generic * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#site_info_def][gLite site-info.def variables]] * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#VO_related_variables][gLite VO-related variables]] * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#site_info_pre][gLite site-info.pre variables]] * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#site_info_post][gLite site-info.post variables]] | *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*: <pre># lsb_release -i | cut -f2 ScientificSL</pre> More details here: "[[http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_the_OS_name][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*: <pre># uname -m i686</pre> More details here: "[[http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_my_machine_architecture][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*: <pre># lsb_release -r | cut -f2 4.5</pre> More details here: "[[http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_the_OS_name][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*: <pre># lsb_release -c | cut -f2 Beryllium</pre> More details here: "[[http://goc.grid.sinica.edu.tw/gocwiki/How_to_publish_the_OS_name][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). <BR/> *ATTENTION*: if you have more than one CE and shared WNs set this variable to "0". <BR/> More details here: <BR/>"[[http://gstat.gridops.org/gstat/filter_help.html#GIISQuery_Usage][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 separated 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* | *Description* | *>= ig-yaim version*| | ''BATCH_LOG_DIR'' | *C* | Path for the batch-system log files: "/var/torque" (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 | ---+++++BDII Site Specific variables are in the configuration file: * ''/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site'' Please copy and edit that file in your ''<confdir>/services'' directory (have a look to [[#Configuration_files][Yaim configuration files]]"). * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#site_BDII][gLite BDII Site variables]] | *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: <pre>BDII_CE_URL="ldap://$CE_HOST:2170/mds-vo-name=resource,o=grid"</pre> | 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:* <pre>SITE_OTHER_GRID="EGEE" </pre> | 4.0.4-0 | | ''SITE_OTHER_EGEE_ROC'' | *C* | Agree within your ROC what the field should be. *USE:* <pre> SITE_OTHER_EGI_ROC="Italy" </pre> | 4.0.4-0 | ---+++++BDII Top * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#top_BDII][gLite BDII Top variables]] By default, a BDII_top is configured to contact the GOC_DB. If you want to modify this behaviour, after the configuration you have to edit the */etc/glite/glite-info-update-endpoints.conf* file using the following settings: <pre> [configuration] EGI = FALSE OSG = FALSE manual = True manual_file = /opt/glite/yaim/config/>file_containing_your_sites.conf> output_file = /opt/glite/etc/gip/top-urls.conf cache_dir = /var/cache/glite/glite-info-update-endpoints </pre> The file containing the list of sites "known" to the BDII_top is updated every hour by the cron-job /etc/cron.hourly/glite-info-update-endpoints. ---+++++DGAS services on CE ( CE CREAM ) | *Variable name* | *Type* | *Descpription* | *>= ig-yaim version* | | ''DGAS_ACCT_DIR'' | *C* | Path for the batch-system log files. <BR/> - for torque/pbs: <pre>DGAS_ACCT_DIR=/var/torque/server_priv/accounting</pre> - for LSF:<pre>DGAS_ACCT_DIR=lsf_install_path/work/cluster_name/logdir</pre> | 4.0.8-3 | | ''DGAS_IGNORE_JOBS_LOGGED_BEFORE'' | O | Bound date on jobs backward processing. <BR/> The backward processing doesn't consider jobs prior to that date. <BR/> Use the format as in this example: <pre>DGAS_IGNORE_JOBS_LOGGED_BEFORE="2007-01-01"</pre> Default value: ''2008-01-01'' | 4.0.2-9 | | ''DGAS_JOBS_TO_PROCESS'' | O | Specify the type of job which the CE has to process. <BR/> *ATTENTION*: set "all" on "the main CE" of the site (the one with the best hardware), "grid" on the others. <BR/> Default value: ''all'' | 4.0.2-9 | | ''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. <BR/> *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.). <BR/> 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). <BR/> Otherwise leave it commented. <BR/> For example: <pre>DGAS_USE_CE_HOSTNAME="my-ce.my-domain"</pre> | 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 | ---+++++GLEXEC_wn * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#GLEXEC_wn][gLite GLEXEC variables]] *Functional Description*: * The *gLExec system*, used in combination with the LCAS site-local authorization system and the LCMAPS local credential mapping service, provides an integrated solution for site access control to grid resources. With the introduction of gLExec, the submission model can be extended from the traditional gatekeeper models, where authorization and credential mapping only take place at the site’s ‘edge’. Retaining consistency in access control, gLExec allows a larger variety of job submission and management scenarios that include per-VO schedulers on the site and the late binding of workload to job slots in a scenario where gLExec in invoked by pilot jobs on the worker node. But it is also the mapping ingredient of a new generation of resource access services, like CREAM. More details [[https://twiki.cern.ch/twiki/bin/view/EGEE/GLExec][here]]. ---+++++UI * [[https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#UI][gLite UI variables]]
Edit
|
Attach
|
PDF
|
H
istory
:
r12
<
r11
<
r10
<
r9
<
r8
|
B
acklinks
|
V
iew topic
|
More topic actions...
Topic revision: r9 - 2012-01-18
-
SergioTraldi
Home
Site map
CEMon web
CREAM web
Cloud web
Cyclops web
DGAS web
EgeeJra1It web
Gows web
GridOversight web
IGIPortal web
IGIRelease web
MPI web
Main web
MarcheCloud web
MarcheCloudPilotaCNAF web
Middleware web
Operations web
Sandbox web
Security web
SiteAdminCorner web
TWiki web
Training web
UserSupport web
VOMS web
WMS web
WMSMonitor web
WeNMR web
IGI Documentation
Repositories specifications
Installation and Configuration Guides
Updates Guides
Services/Node Types List
IGI Updates Calendar
Tips & Tricks
Use Cases & Troubleshooting
Site Admin Corner
IGI Release Management
Integration Process
TODO List
IGI Testing & Certification
Certification Testbed
Blah testing
CREAM testing
HLR testing
Storm testing
UI testing
VOMS testing
WMS testing
WN testing
IGIRelease Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Edit
Attach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback