Tags:
, view all tags

IGI (based on gLite 3.2 release) Installation and Configuration

Installation

OS installation

Install SL5 using SL5.X repository (CERN mirror) or one of the supported OS (RHEL5 clones).

You may find information on official repositories at Repositories for APT and YUM
If you want to set up a local installation server please refer to Mrepo Quick Guide

NOTE: Please check if NTP , cron and logrotate are installed, otherwise install them!

Check the FQDN hostname

Ensure that the hostnames of your machines are correctly set. Run the command:

 hostname -f

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 Repository Specifications

With standard installation of SL5 it's possible that you have the EPEL repository enabled. Please disable it:

# mv /etc/yum.repos.d/epel.repo /etc/yum.repos.d/epel.repo.disabled

otherwise you'll get the following error:

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)

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*
dag.repo
ig.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:

MetapackagesSorted ascending Profile-specific repositories *x86_64*
ig_ARGUS glite-argus.repo
ig_BDII_site glite-bdii_site.repo
ig_BDII_top glite-bdii_top.repo
ig_CREAM
ig_CREAM_LSF
glite-cream.repo
ig_CREAM_torque glite-cream_torque.repo
ig_FTA_oracle glite-fta_oracle.repo
ig_FTM glite-ftm.repo
ig_FTS_oracle glite-fts_oracle.repo
ig_GLEXEC_wn glite-glexec.repo
ig_HLR glite-generic.repo
ig_LB glite-lb.repo
ig_LFC_mysql glite-lfc_mysql.repo
ig_SE_dcache_info glite-se_dcache_info.repo
ig_SE_dcache_nameserver_chimera glite-se_dcache_nameserver.repo
ig_SE_dcache_pool glite-se_dcache_pool.repo
ig_SE_dcache_srm glite-se_dcache_srm.repo
ig_SE_dpm_mysql glite-se_dpm_mysql.repo
ig_SE_storm_backend
ig_SE_storm_frontend
ig_SE_storm_checksum
ig-storm.repo
ig_SE_storm_gridftp ig-storm_gridftp.repo
ig_UI
ig_UI_noafs
glite-ui.repo
ig_VOBOX glite-vobox.repo
ig_VOMS_mysql glite-voms_mysql.repo
ig_VOMS_oracle glite-voms_oracle.repo
ig_WN_torque, ig_WN_torque_noafs glite-wn_torque.repo
ig_WN, ig_WN_noafs
ig_WN_LSF, ig_WN_LSF_noafs
glite-wn.repo

Then update your host:

yum clean all

CAa installation:

Install CAs on ALL profiles:

yum install ca-policy-egi-core

Metapackage installation

Please consider that x86_64 WN profiles has to be installed using the “groupinstall” yum command as follows:

 yum groupinstall <WN_profile>  

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

 yum groupinstall <UI_profile>  

where <UI_profile> could be one of: ig_UI, ig_UI_noafs

If you are installing any othere profiles use:

 yum install <metapackage> 

Where <metapackage> is one of those reported on the table above ( Metapackages column).

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.
It's a mandatory file.
It's a parameter passed to the ig_yaim command.
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.
For example you may use vimdiff:
vimdiff /opt/glite/yaim/examples/siteinfo/ig-site-info.def <confdir>/<your-site-info.def>
<your-wn-list.conf> whole-site Worker nodes list in the format of hostname.domainname per row.
It's a mandatory file.
It's defined by WN_LIST variable in <your-site-info.def>.
<your-users.conf> whole-site Pool account user mapping.
It's a mandatory file.
It's defined by USERS_CONF variable in <your-site-info.def>.
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: Whole site: How to create local users.conf and configure users.
<your-groups.conf> whole-site VOMS group mapping.
It's a mandatory file.
It's defined by GROUPS_CONF variable in <your-site-info.def>.
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.
The file contains a list of configuration variables specific to that nodetype.
Each yaim module distributes a configuration file in =/opt/glite/yaim/examples/siteinfo/services/[ig or glite]-node-type.
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.
The file contains host specific variables that are different from one host to another in a certain site.
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 ”lights.infn.it”:
# cat vo.d/lights.infn.it
SW_DIR=$VO_SW_DIR/lights
DEFAULT_SE=$SE_HOST
VOMS_SERVERS="vomss://voms2.cnaf.infn.it:8443/voms/lights.infn.it?/lights.infn.it"
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"

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.

group.d/ VO-specific It contains a file per VO with the name format: groups-<vo_name>.conf.
The file contains VO specific groups and it replaces the former <your-groups.conf> file where all the VO groups were specified all together.
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:
If your site has the intention to support more VOs than the default ones, you should have a look at Whole site: How to enable a VO, specially for the enmr.eu VO, once the configuration finished you should follow extra_configuration.

-- CristinaAiftimiei - 2011-11-10

Edit | Attach | PDF | History: r12 | r6 < r5 < r4 < r3 | Backlinks | Raw View | More topic actions...
Topic revision: r4 - 2011-11-10 - SergioTraldi
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback