Difference: IgiEmi (1 vs. 77)

Revision 772014-02-14 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 780 to 780
 
  • For Other Batch System:
 /opt/glite/yaim/bin/yaim -c -d 6 -s    -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
Added:
>
>

Known Issues

  • ig_WN SL6 version:
    • misses the dependency on HEP_OSLib, available from linuxsoft/wlcg. One has to install the latest version available there.
    • in SL6 there is no portmap daemon. It should be replaced with rpcbind in the yaim configuration function config_nfs_sw_dir_client. It should be fixed in a future version of the yaim-addons package.
 

Service Testing - Reference Card

After service installation you could have a look at WN - Service Reference Card. In this page you can find information on what daemons are running, log files, cron jobs, etc.

Revision 762013-06-07 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 109 to 109
 
File or Directory Scope Example
<-- -->
Sorted ascending
Details
<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-site-info.def> whole-site ig-site-info.def 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>
Changed:
<
<
<your-users.conf> whole-site ig-users.conf 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: ”<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-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful

Revision 752013-06-07 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 109 to 109
 
File or Directory Scope Example Details
<your-site-info.def> whole-site ig-site-info.def 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>.
Changed:
<
<
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful
>
>
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful
  Known issues
  • BDII_DELETE_DELAY default value is missing for services other than BDII site & top.

Revision 742013-04-12 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 109 to 109
 
File or Directory Scope Example Details
<your-site-info.def> whole-site ig-site-info.def 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>.
Changed:
<
<
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
>
>
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
 
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful

Known issues

Revision 732013-02-26 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 1113 to 1113
 
  • Just update the packages:
    # yum update
Deleted:
<
<
  • And reconfigure:
     # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  HLR 2>&1 | tee /root/conf_igi-HLR.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

HLR Documentation References:

Changed:
<
<
>
>
 
META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 722013-02-26 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 1062 to 1062
 
# dgas-hlr-addadmin -Sa  <CE_DN>
  • Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"
Changed:
<
<

Update From a previous release (< 4.0):

>
>

Update From a previous release < 4.0:

 
  • IMPORTANT NOTE: some of the operations described bellow (like "translate DB", the start of hlrd or "populateJobTransSummary") can take a lot of time, from minutes to hours or days (!) depending on how big the DB is. Please plan carefully an upgrade!
Line: 1109 to 1109
  Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"
Added:
>
>

Update From a previous release >= 4.0.13:

  • Just update the packages:
    # yum update
  • And reconfigure:
     # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  HLR 2>&1 | tee /root/conf_igi-HLR.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

HLR Documentation References:

Revision 712013-02-26 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 962 to 962
 
Changed:
<
<

HLR Server Installation and Configuration NEW

>
>

HLR Server Installation and Configuration NEW Update

 

Extended Release Notes:

Added:
>
>
 

HLR Prerequisites

Revision 702013-01-25 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 67 to 67
 
SL5 x86_64 SL6 x86_64
EMI1 EMI2 EMI2
Changed:
<
<
EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 6 repo - please use epel-release-6-7.noarch.rpm
>
>
EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 6 repo - please use epel-release-6-8.noarch.rpm
 
EMI 1 repos - please use emi-release-1.0.1-1.sl5.noarch.rpm EMI 2 repos - please use emi-release-2.0.0-1.sl5.noarch.rpm EMI 2 repos - please install this emi-release-2.0.0-1.sl6.noarch.rpm
EGI trust anchors repo - egi-trustanchors.repo EGI trust anchors repo - egi-trustanchors.repo EGI trust anchors repo - egi-trustanchors.repo
IGI (1) repo - igi-emi.repo IGI (2) repo igi-emi2.repo IGI (2) repo - igi-emi2.repo

Revision 692012-11-29 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 111 to 111
 
<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 ig-users.conf 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: ”<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 ig-groups.conf 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.
Changed:
<
<
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful
>
>
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful
  Known issues
  • BDII_DELETE_DELAY default value is missing for services other than BDII site & top.

Revision 682012-11-21 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 50 to 50
  EPEL has an epel-release package that includes the gpg key used for package signing and other repository information, like the .repo files.
Tto use normal tools such as yum to install packages and their dependencies
Changed:
<
<
>
>
  By default the stable EPEL repo is enabled. Example of epel-5.repo file:
[extras]

Line: 67 to 67
 
SL5 x86_64 SL6 x86_64
EMI1 EMI2 EMI2
Changed:
<
<
EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 6 repo - please use epel-release-6-7.noarch.rpm
>
>
EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 6 repo - please use epel-release-6-7.noarch.rpm
 
EMI 1 repos - please use emi-release-1.0.1-1.sl5.noarch.rpm EMI 2 repos - please use emi-release-2.0.0-1.sl5.noarch.rpm EMI 2 repos - please install this emi-release-2.0.0-1.sl6.noarch.rpm
EGI trust anchors repo - egi-trustanchors.repo EGI trust anchors repo - egi-trustanchors.repo EGI trust anchors repo - egi-trustanchors.repo
IGI (1) repo - igi-emi.repo IGI (2) repo igi-emi2.repo IGI (2) repo - igi-emi2.repo

Revision 672012-11-06 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 1038 to 1038
 
  • For your convenience you can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
     # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  HLR 2>&1 | tee /root/conf_igi-HLR.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
Added:
>
>
Known Issue - IMPORTANT NOTE

After configuration please change into the file /etc/cron.d/dgas the command from /usr/sbin/dgas-hlr-translatedb to /usr/sbin/dgas-hlr-populateJobTransSummary like the example below:

cat /etc/cron.d/dgas 
# Cron file created by YAIM - don't modify it!
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/

# Update hlr database
*/4 * * * * root /usr/sbin/dgas-hlr-populateJobTransSummary > /dev/null 2>&1

This fix will be provide with the new yaim in next release.

 

Post installation and configuration

  • After the installation and configuration of the HLR Server services, you should register all the resources of the CEs attached to your HLR Server. Please use thecommand below for each CE:
Line: 1080 to 1097
 
# /usr/sbin/dgas-hlr-populateJobTransSummary 
  • Restart dgas services :
    # /etc/init.d/dgas-hlrd restart 
Added:
>
>
  • Change the into the file */etc/cron.d/dgas the command from /usr/sbin/dgas-hlr-translatedb to /usr/sbin/dgas-hlr-populateJobTransSummary
 

Post Update Procedure

Revision 662012-10-26 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 1046 to 1046
 

Update From a previous release (< 4.0):

Changed:
<
<
  • IMPORTANT NOTE: some of the operations described bellow (like "translate DB") can take a lot of time, from minutes to hours or days (!) depending on how big the DB is. Please plan carefully an upgrade!
>
>
  • IMPORTANT NOTE: some of the operations described bellow (like "translate DB", the start of hlrd or "populateJobTransSummary") can take a lot of time, from minutes to hours or days (!) depending on how big the DB is. Please plan carefully an upgrade!
 
  • Back up the old databases :
    • on HLR Server stop the dgas services and make a dump of the databases:

Revision 652012-10-25 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 985 to 985
 
  • Please use a physical disk partition for the filesystem hosting the DB

Operating System

Changed:
<
<
  • HLR Server 4.0 is supported on Scientific Linux 5, x86_64.
>
>
  • HLR Server 4.0 is supported on Scientific Linux 5, x86_64 and Scientific Linux 5, x86_64
 

Host certificate installation:

Line: 1009 to 1009
 

Middleware Installation

  • Have a look to the section Repository Settings and ensure that you have the common repo files.
Changed:
<
<
  • You can use any of the group of repositories reccomended for SL5/x86_64 (EMI 1 or EMI 2) section.
>
>
  • You can use any of the group of repositories reccomended for SL5/x86_64 (EMI 1 or EMI 2) section or SL6/x86_64 (EMI 2) section.
 
  • Before starting the installation procedure remember to clean all yum cache and headers:
    # yum clean all
Line: 1029 to 1029
 

Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the HLR profile
Changed:
<
<
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  HLR 
>
>
# /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  HLR 
 
  • If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.

HLR Server Configuration

Line: 1046 to 1046
 

Update From a previous release (< 4.0):

Added:
>
>
  • IMPORTANT NOTE: some of the operations described bellow (like "translate DB") can take a lot of time, from minutes to hours or days (!) depending on how big the DB is. Please plan carefully an upgrade!
 
  • Back up the old databases :
    • on HLR Server stop the dgas services and make a dump of the databases:
      • Stop the services :
Line: 1056 to 1058
 
        • You should have the space to contain the hlr and hlr_tmp database dump. (Mount an external partition or NFS partition if you don't have enough free space)
      • Make the dump :

Changed:
<
<
mysqldump --user=root --password hlr_Padova > /data/hlr.sql mysqldump --user=root --password hlr_tmp_Padova > /data/hlr_tmp.sql
>
>
mysqldump --user=root --password hlr > /data/hlr.sql mysqldump --user=root --password hlr_tmp > /data/hlr_tmp.sql
 
  • Installation :
Changed:
<
<
    • Install again the host with SL5/x86_64 distribution or install a new host where the HLR Server will be installed.
>
>
    • Install again the host with SL5 or SL6, x86_64 distribution or install a new host where the HLR Server will be installed.
 
    • Following the instructions in the previous section install the HLR Server and configure it using yaim.
  • Stop the HLR server process:
    # /etc/init.d/dgas-hlrd stop

Revision 642012-10-25 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 453 to 453
 
# yum clean all
Changed:
<
<
The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64.
  • Please remember that the TORQUE Server and Client work only if the CE and the WNs are SL5 x86_64 and the MAUI version is the same in the server and client nodes. Please update the WN if you have an old installation.
>
>
The CREAM CE Services were tested with gLite WN SL5/SL6 x86_64 and also with ig_WN SL5/SL6 x86_64.
 

CREAM CE Prerequisites

Line: 663 to 662
 

WN Installation and Configuration

Changed:
<
<
Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:
>
>
  • Supported platforms: SL5/x86_64 & SL6/x86_64
 
Changed:
<
<
# yum clean all
>
>
  • Have a look to the section Repository Settings and ensure that you have the common repo files.
  • Before starting the installation procedure remember to clean all yum cache and headers:
    # yum clean all
 

WN Prerequisites

Line: 680 to 678
 

CAs installation:

Changed:
<
<
  • Install CAs on ALL profiles:
# yum install ca-policy-egi-core
>
>
  • Install CAs on ALL profiles:
    # yum install ca-policy-egi-core
 

Service installation

Changed:
<
<
  • Have a look to the WN documentation before starting the installationl: WN Guide.
  • Install the WN metapackages, containing all packages needed:
# yum install <metapackage> emi-version;
  • IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of these (see table bellow)
>
>

  • Install the WN metapackage:
    • EMI 1:
      # yum install <metapackage> emi-version openldap-client python-ldap 
    • EMI 2:
      # yum install <metapackage> 

  • IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster (see table bellow)
 
    • IGI customizations:
      • unique metapackages & configurations for WNs with support for the batch systems Torque & LSF
Changed:
<
<
      • contains the "LCG Applications Dependency Metapackage" - HEP_OSLib, compat-gcc-34-g77, compat-libgcc-296, compat-libstdc++-296, gcc-c++, ghostscript lapack, ncurses, openafs, openafs-client, openldap-clients
      • contains yaim-addons - new configuration package with IGI-custom configuration functions and files (replaces ig-yaim)
>
>
      • contains (where available) the "LCG Applications Dependency Metapackage" - HEP_OSLib, compat-gcc-34-g77, compat-libgcc-296, compat-libstdc++-296, gcc-c++, ghostscript lapack, ncurses, openafs, openafs-client, openldap-clients
      • contains yaim-addons - new configuration package with IGI-custom configuration functions and files (replaces ig-yaim), like - "ssh passwordless"
 
Line: 711 to 713
 
IMPORTANT NOTE:
Changed:
<
<
Name are case sensitive, both for metapackages installation and notetype configuration, you have to use the ones in the table above.
>
>
Metapackages & Notetypes Names are case sensitive, both for metapackages installation and notetype configuration, PLEASE use the ones in the table above.
 

IMPORTANT NOTE FOR TORQUE:
Changed:
<
<
After the Torque installation you should have the version 2.5.7-7.
Please remember to copy the munge key from the batch master to the WN just installed
# scp <batch master host>:/etc/munge/munge.key /etc/munge 
>
>
After the Torque installation you should have the version 2.5.7-7 (SL5) or 2.5.7-9 (SL5)
Please remember to copy the munge key from the batch master to the WN just installed
# scp <batch master host>:/etc/munge/munge.key /etc/munge 

For more details please read Deployment Notes of TORQUE WN config - it applies to all versions >= 2.5.7-1
 

Service Configuration

Line: 728 to 730
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the WN profiles (WN_torque, WN_torque_noafs, WN_LSF, WN_LSF_noafs)
Changed:
<
<
For Torque:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque 
>
>
  • For Torque:
    # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN_torque 
 or
Changed:
<
<
# /glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque_noafs 
>
>
# /glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN_torque_noafs 
 
Changed:
<
<
For LSF:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF
>
>
  • For LSF:
    # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN_LSF
 or
Changed:
<
<
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF_noafs
>
>
# /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN_LSF_noafs
 
Changed:
<
<
For Other Batch System:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN
>
>
  • For Other Batch System:
    # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN
 
Changed:
<
<
You can find in this documentation: YAIM WN Variables all mandatory variables.
>
>
You can find all mandatory variables in this documentation: YAIM WN Variables
 
Changed:
<
<
If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.
>
>
If no errors are reported during verification you can proceed with the configuration, otherwise correct them before continuing.
 

YAIM Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
Changed:
<
<
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
>
>
  • For your convenience you can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
 
IMPORTANT NOTE:
Changed:
<
<
All the nodetypes name are case sensitive, you have to write it as described above.
>
>
All the nodetypes name are case sensitive, you have to write them as described above.
 
Changed:
<
<
  • For Torque:
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
  • For Torque:
     # /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 or
Changed:
<
<
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log

IMPORTANT NOTE:
SL6/x86_64 first configuration with yaim presents the following WARNING:
 WARNING: /var/lib/torque/mom_priv/config already exists, YAIM will not touch it
 WARNING: Batch server defined in BATCH_SERVER variable is different 
 WARNING: from the batch server defined under /var/lib/torque/mom_priv/config
 WARNING: Remove /var/lib/torque/mom_priv/config and reconfigure again to use the new value! 

this is due to the presence of the file /var/lib/torque/mom_priv/config, provided by the SL6 torque-mom package, torque-mom-2.5.7-9.el6.x86_64. Remove the file as recommended and reconfigure
 
Changed:
<
<
  • For LSF:
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
  • For LSF:
     # /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def> -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 or
Changed:
<
<
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 
  • For Other Batch System:
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 /opt/glite/yaim/bin/yaim -c -d 6 -s    -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information.
>
>
After service installation you could have a look at WN - Service Reference Card. In this page you can find information on what daemons are running, log files, cron jobs, etc.
 

WN Documentation References:

Added:
>
>
 
Deleted:
<
<
 
Changed:
<
<
  • Other Documentation available here
>
>
 

UI Installation and Configuration

Added:
>
>
  • Supported platforms: SL5/x86_64 & SL6/x86_64
 
  • Have a look to the section Repository Settings and ensure that you have the common repo files
Changed:
<
<
  • Before starting the installation procedure remember to clean all yum cache and headers:
# yum clean all
>
>
  • Before starting the installation procedure remember to clean all yum cache and headers:
    # yum clean all
 

CAs installation:

Changed:
<
<
  • Install CAs on ALL profiles:
# yum install ca-policy-egi-core
>
>
  • Install CAs on ALL profiles:
    # yum install ca-policy-egi-core
 

Service installation

  • Have a look to the UI documentation before starting to install: UI Guides.
Changed:
<
<
  • Install the UI metapackages, containing all packages needed.

# yum install emi-ui
>
>
  • Install the UI metapackages, containing all clients available:
    # yum install emi-ui
 

Service Configuration

YAIM Verification

Changed:
<
<
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for the UI profile

 # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  UI 
>
>
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for the UI nodetype:
     # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  UI 
 
Changed:
<
<
You can find in this documentation: YAIM UI Variables all mandatory variables.
>
>
You can find all mandatory variables in this documentation: YAIM UI Variables
 
Changed:
<
<
If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing.
>
>
If no errors are reported during verification you can proceed with the configuration, otherwise correct them before continuing.
 

YAIM Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
Changed:
<
<
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.

 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
>
>
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations:
     /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def>  -n  UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
 

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can find some commonl errors and other useful service information.
>
>
After service installation you could have a look at the UI Reference Card or User Troubleshooting Guide. In this page you can find some common errors and other useful service information.
 

UI Documentation References:

Revision 632012-10-23 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 1064 to 1064
  # mysql -u root -p hlr < /data/hlr.sql
  • execute translate DB
Changed:
<
<
# nohup /usr/sbin/dgas-hlr-translatedb --D & 
>
>
# nohup /usr/sbin/dgas-hlr-translatedb -D & 
 
  • Start dgas services :
    # /etc/init.d/dgas-hlrd start 
  • Execute populateJobTransSummary:

Revision 622012-10-17 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 554 to 553
  # yum install emi-lsf-utils
Changed:
<
<

DGAS_sensors installation UPDATED

IGI Release supports the use of DGAS as accounting system - please install also DGAS sensors on the CREAM node. You can found more documentation to DGAS Sensors 4.0 guide

>
>

DGAS_sensors installation & upgrade

Extended Release Notes:
 
Added:
>
>
IGI Release supports the use of DGAS as accounting system - please install also DGAS sensors on the CREAM node:
 
# yum install igi-dgas_sensors
Added:
>
>
Upgrade:
  • in case of an upgrade from a version < 3 - please follow section 3.1.1.2 Upgrade from a previous release from DGAS Sensors 4.0 guide
  • in case of an upgrade from 4.0.x to 4.0.13, after the updated packages are installed just restart the services:
       # service dgas-urcollector restart
       # service dgas-pushd restart
       

You can found more documentation at DGAS Sensors 4.0 guide and on DGAS Sensors Service Reference Card

 

Middleware Configuration

YAIM Verification

Line: 647 to 657
  * Service Troubleshooting Guide
* Other Documentation available here
Added:
>
>

DGAS Sensors Documentation References:

 

WN Installation and Configuration

Have a look to the section Repository Settings and ensure that you have the common repo files.

Line: 943 to 957
 

HLR Server Installation and Configuration NEW

Added:
>
>

Extended Release Notes:

 

HLR Prerequisites

Revision 612012-10-17 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 987 to 987
 

Middleware Installation

  • Have a look to the section Repository Settings and ensure that you have the common repo files.
Changed:
<
<
  • Please use the repositories reccomended in the EMI 2 section.
>
>
  • You can use any of the group of repositories reccomended for SL5/x86_64 (EMI 1 or EMI 2) section.
 
  • Before starting the installation procedure remember to clean all yum cache and headers:
    # yum clean all

Revision 602012-10-17 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 554 to 554
  # yum install emi-lsf-utils
Changed:
<
<

DGAS_sensors installation NEW

>
>

DGAS_sensors installation UPDATED

  IGI Release supports the use of DGAS as accounting system - please install also DGAS sensors on the CREAM node. You can found more documentation to DGAS Sensors 4.0 guide
Line: 942 to 942
 
Changed:
<
<

HLR Server Installation and Configuration

>
>

HLR Server Installation and Configuration NEW

 

HLR Prerequisites

Line: 988 to 988
 
  • Have a look to the section Repository Settings and ensure that you have the common repo files.
  • Please use the repositories reccomended in the EMI 2 section.
Changed:
<
<
  • Before starting the installation procedure remember to clean all yum cache and headers:

# yum clean all
>
>
  • Before starting the installation procedure remember to clean all yum cache and headers:
    # yum clean all
 

CAs installation:

Changed:
<
<
  • Install CAs on ALL profiles:
# yum install ca-policy-egi-core
>
>
  • Install CAs on ALL profiles:
    # yum install ca-policy-egi-core
 

HLR Server installation

Changed:
<
<
  • Install the HLR metapackages, containing all packages needed:
# yum install igi-hlr
>
>
  • Install the HLR metapackages, containing all packages needed:
    # yum install igi-hlr
 

Middleware Configuration

Verification

Changed:
<
<
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the HLR profile
>
>
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the HLR profile
 
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  HLR 
Deleted:
<
<
 
  • If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.

HLR Server Configuration

Line: 1021 to 1013
 

HLR Server Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
Changed:
<
<
  • For your convenience you can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.

>
>
  • For your convenience you can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
 
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  HLR 2>&1 | tee /root/conf_igi-HLR.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log

Post installation and configuration

Changed:
<
<
After the installation and configuration of the HLR Server services, you should register all the resources of the CEs attached to your HLR Server. Please use this command below for each CE:
# dgas-hlr-addadmin -Sa  <CE_DN>

Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"

>
>
  • After the installation and configuration of the HLR Server services, you should register all the resources of the CEs attached to your HLR Server. Please use thecommand below for each CE:
    # dgas-hlr-addadmin -Sa  <CE_DN>
  • Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"
 

Update From a previous release (< 4.0):

  • Back up the old databases :
    • on HLR Server stop the dgas services and make a dump of the databases:
Changed:
<
<
      • Stop the services :
# /etc/init.d/glite-dgas-hlrd stop
>
>
      • Stop the services :
        # /etc/init.d/glite-dgas-hlrd stop 
 
      • Check disk space
Changed:
<
<
        • Ensure you have enough space in the disk:
# df -h
You should have the space to contain the hlr and hlr_tmp database dump. (Mount an external partition or NFS partition if you don't have enough free space)
      • Make the dump :
>
>
        • Ensure you have enough space in the disk:
          # df -h
        • You should have the space to contain the hlr and hlr_tmp database dump. (Mount an external partition or NFS partition if you don't have enough free space)
      • Make the dump :
 
mysqldump --user=root --password hlr_Padova > /data/hlr.sql
mysqldump --user=root --password hlr_tmp_Padova > /data/hlr_tmp.sql
  • Installation :
    • Install again the host with SL5/x86_64 distribution or install a new host where the HLR Server will be installed.
Changed:
<
<
+ Following the instructions in the previous section install the HLR Server and configure it using yaim.
  • Stop the HLR server process:
# /etc/init.d/dgas-hlrd stop
  • Restore the dump :
>
>
    • Following the instructions in the previous section install the HLR Server and configure it using yaim.
  • Stop the HLR server process:
    # /etc/init.d/dgas-hlrd stop
  • Restore the dump :
 
# mysql -u root -p hlr_tmp < /data/hlr_tmp.sql
# mysql -u root -p hlr < /data/hlr.sql
Changed:
<
<
  • execute translate DB
]# nohup /usr/sbin/dgas-hlr-translatedb --D &
  • Start dgas services :
# /etc/init.d/dgas-hlrd start
>
>
  • execute translate DB
    # nohup /usr/sbin/dgas-hlr-translatedb --D & 
  • Start dgas services :
    # /etc/init.d/dgas-hlrd start 
 
  • Execute populateJobTransSummary:
Changed:
<
<
# /usr/sbin/dgas-hlr-populateJobTransSummary
  • Restart dgas services :
# /etc/init.d/dgas-hlrd restart
>
>
    • The new HLR version need to polulate the JobTransSummary
      # /usr/sbin/dgas-hlr-populateJobTransSummary 
  • Restart dgas services :
    # /etc/init.d/dgas-hlrd restart 
 

Post Update Procedure

Changed:
<
<
After the update of the HLR Server Services, you should register again all the resources of the CE attached to your HLR Server. Please use this command below for each CE:
>
>
After the update of the HLR Server , you should register again all the resources of the CE attached to your HLR Server. Please use this command below for each CE:
 
# dgas-hlr-addadmin -Sa  <CE_DN>

Revision 592012-10-17 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 447 to 447
 
Changed:
<
<

CREAM CE Installation and Configuration

>
>

CREAM CE using DGAS accounting - Installation and Configuration

  Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:
Changed:
<
<
yum clean all
>
>
# yum clean all
  The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64.
  • Please remember that the TORQUE Server and Client work only if the CE and the WNs are SL5 x86_64 and the MAUI version is the same in the server and client nodes. Please update the WN if you have an old installation.
Line: 462 to 461
 

Host certificate installation:

Changed:
<
<
All nodes except UI, WN and BDII require the host certificate/key files to be installed.
Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.
>
>
  • All nodes except UI, WN and BDII require the host certificate/key files to be installed*
  • Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.
  Once you have obtained a valid certificate:
Line: 508 to 505
 
yum install ca-policy-egi-core
Changed:
<
<

Service installation

>
>

Middleware installation

 
  • Install the CREAM CE metapackages, containing all packages needed. Have a look to the CREAM CE documentation before starting to install :System Administrator Guide.

Changed:
<
<
yum install xml-commons-apis yum install emi-cream-ce
>
>
# yum install xml-commons-apis # yum install emi-cream-ce
 

Batch System Utilities installation

Line: 523 to 520
 
  • If you are running Torque, and your CREAM CE node is the torque master, install the emi-torque-server and emi-torque-utils metapackages:


Changed:
<
<
yum install emi-torque-server yum install emi-torque-utils
>
>
# yum install emi-torque-server # yum install emi-torque-utils
 

  • If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage:


Changed:
<
<
yum install emi-torque-utils
>
>
# yum install emi-torque-utils
 

IMPORTANT NOTE FOR TORQUE:

After the Torque installation you should have the version 2.5.7-7. Please check that munge is installed and enabled.


Changed:
<
<
rpm -qa | grep munge munge-libs-0.5.8-8.el5 munge-0.5.8-8.el5
>
>
# rpm -qa | grep munge # munge-libs-0.5.8-8.el5 # munge-0.5.8-8.el5
 

To enable munge on your torque cluster:

Line: 552 to 549
 
  • Start the munge daemon on these nodes. *service munge start && chkconfig munge on*
Changed:
<
<
  • If you are running LSF, install the emi-lsf-utils metapackage:
>
>
  • If you are running LSF, install the emi-lsf-utils metapackage:
 

Changed:
<
<
yum install emi-lsf-utils
>
>
# yum install emi-lsf-utils
 
Changed:
<
<

DGAS_sensors installation

>
>

DGAS_sensors installation NEW

 
Changed:
<
<
If you use DGAS to account data remember to install also DGAS sensors. You can found more documentation to DGAS sensors guide
>
>
IGI Release supports the use of DGAS as accounting system - please install also DGAS sensors on the CREAM node. You can found more documentation to DGAS Sensors 4.0 guide
 

Changed:
<
<
yum install igi-dgas_sensors
>
>
# yum install igi-dgas_sensors
 
Changed:
<
<

Service Configuration

>
>

Middleware Configuration

 

YAIM Verification

Line: 952 to 948
 

Hardware Requirements

Changed:
<
<
The HLR server host should be a real or virtual node having an optimal disk access.
>
>
  • The HLR Server host should be a real or virtual node having an optimal disk access.
  • The suggested requirements are:
    • CPU: 4/8 cores
    • Memory: 8/16GB RAM
    • Disk: minimum 200 GB of space for a first level HLR. (if you have an old HLR server please check your database actual dimension and redouble the partition size)
    • Network: open port TCP 56568 for inbuond connectivity
 
Deleted:
<
<
The suggested requirements are:
  • 4/8 cores CPU
  • 8/16GB RAM
  • minimum 200 GB of space for a first level HLR. (if you have an old HLR server please check your database actual dimension and redouble the partition size)
 

Co-Hosting

Changed:
<
<
Due to the critical nature the HLR server should be installed as a stand-alone service.
>
>
  • Due to its critical nature the HLR Server should be installed as a stand-alone service.
 

Virtual vs. Physical

Changed:
<
<
If you will use a virtual host ensure you are not using virtio to access to the mysql storage DB. Please use a physical partition.
>
>
  • If you will use a virtual host ensure you are not using Virtio to access to the mysql storage DB.
  • Please use a physical disk partition for the filesystem hosting the DB
 
Changed:
<
<

Host certificate installation:

>
>

Operating System

  • HLR Server 4.0 is supported on Scientific Linux 5, x86_64.
 
Changed:
<
<
The HLR host must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:
>
>

Host certificate installation:

 
Changed:
<
<
Check existence
>
>
  • The HLR host must be configured with X.509 certificates signed by a trusted Certification Authority (CA).
  • The hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:
  • Check existence
 

Changed:
<
<
[~]# ls -l /etc/grid-security/hostkey.pem
>
>
# ls -l /etc/grid-security/hostkey.pem
 -r-------- 1 root root 887 Mar 1 17:08 /etc/grid-security/hostkey.pem
Changed:
<
<
[~]# ls -l /etc/grid-security/hostcert.pem
>
>
# ls -l /etc/grid-security/hostcert.pem
 -rw-r--r-- 1 root root 1440 Mar 1 17:08 /etc/grid-security/hostcert.pem
Changed:
<
<
Check expiration
>
>
  • Check expiration
 
[~]# openssl x509 -in hostcert.pem -noout -dates
Changed:
<
<
Change permission: (if needed)
>
>
  • Change permission: (if needed)
 

Changed:
<
<
[~]# chmod 0400 hostkey.pem [~]# chmod 0600 hostcert.pem
>
>
# chmod 0400 hostkey.pem # chmod 0600 hostcert.pem
 

Middleware Installation

Changed:
<
<
Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:
>
>
  • Have a look to the section Repository Settings and ensure that you have the common repo files.
  • Please use the repositories reccomended in the EMI 2 section.
  • Before starting the installation procedure remember to clean all yum cache and headers:
 
# yum clean all

Line: 1001 to 1002
 

HLR Server installation

Changed:
<
<
  • Have a look to the HLR documentation before starting the installation: Service Guide.
>
>
 
  • Install the HLR metapackages, containing all packages needed:

Changed:
<
<
# yum install igi-hlr;
>
>
# yum install igi-hlr
 

Middleware Configuration

Line: 1015 to 1016
 
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  HLR 
Changed:
<
<
If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.
>
>
  • If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.
 

HLR Server Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
Changed:
<
<
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
>
>
  • For your convenience you can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
 
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  HLR 2>&1 | tee /root/conf_igi-HLR.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
Line: 1033 to 1034
  Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"
Changed:
<
<

Update From previous release:

Back up the old databases :

>
>

Update From a previous release (< 4.0):

 
Changed:
<
<
Form previous HLR Server stop the dgas services and make a dump of the databases:

Stop the services :

>
>
  • Back up the old databases :
    • on HLR Server stop the dgas services and make a dump of the databases:
      • Stop the services :
 
# /etc/init.d/glite-dgas-hlrd stop
Changed:
<
<
Check disk space Ensure you have enough space in the disk:
>
>
      • Check disk space
        • Ensure you have enough space in the disk:
 
# df -h
You should have the space to contain the hlr and hlr_tmp database dump. (Mount an external partition or NFS partition if you don't have enough free space)
Changed:
<
<
Make the dump :
>
>
      • Make the dump :
 
mysqldump --user=root --password hlr_Padova > /data/hlr.sql
mysqldump --user=root --password hlr_tmp_Padova > /data/hlr_tmp.sql
Changed:
<
<
Installation : Install again the host with SL5 x86_64 SL distribution or install a new host where the HLR Server will be installed.

Following the above instructions install the HLR Server and configure using yaim.

Stop the HLR server process:

>
>
  • Installation :
    • Install again the host with SL5/x86_64 distribution or install a new host where the HLR Server will be installed. + Following the instructions in the previous section install the HLR Server and configure it using yaim.
  • Stop the HLR server process:
 
# /etc/init.d/dgas-hlrd stop
Changed:
<
<
Restore the dump :
>
>
  • Restore the dump :
 
# mysql -u root -p hlr_tmp < /data/hlr_tmp.sql
# mysql -u root -p hlr < /data/hlr.sql
Changed:
<
<
execute translate DB
>
>
  • execute translate DB
 
]# nohup /usr/sbin/dgas-hlr-translatedb --D &
Changed:
<
<
Start dgas services :
>
>
  • Start dgas services :
 
# /etc/init.d/dgas-hlrd start
Changed:
<
<
Execute populateJobTransSummary:

The new HLR version need to polulate the JobTransSummary

>
>
  • Execute populateJobTransSummary:
 
# /usr/sbin/dgas-hlr-populateJobTransSummary
Changed:
<
<
Restart dgas services :
>
>
  • Restart dgas services :
 
# /etc/init.d/dgas-hlrd restart
Line: 1106 to 1094
 

HLR Documentation References:

Changed:
<
<
>
>
 
META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 582012-10-16 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 67 to 67
 
SL5 x86_64 SL6 x86_64
EMI1 EMI2 EMI2
Changed:
<
<
epel-5.repo - please install epel-release-5-4.noarch.rpm epel-5.repo - please install epel-release-5-4.noarch.rpm epel-6.repo - please install epel-release-6-7.noarch.rpm
EMI 1 repos - emi1-base.repo, emi1-updates.repo, emi1-third-party.repo
Please install emi-release-1.0.1-1.sl5.noarch.rpm
EMI 2 repos - emi2-base.repo, emi2-updates.repo, emi2-third-party.repo
Please install emi-release-2.0.0-1.sl5.noarch.rpm
EMI 2 repos - emi2-base.repo, emi2-updates.repo, emi2-third-party.repo
Please install this emi-release-2.0.0-1.sl6.noarch.rpm
egi-trustanchors.repo egi-trustanchors.repo egi-trustanchors.repo
>
>
EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 5 repo - please use epel-release-5-4.noarch.rpm EPEL 6 repo - please use epel-release-6-7.noarch.rpm
EMI 1 repos - please use emi-release-1.0.1-1.sl5.noarch.rpm EMI 2 repos - please use emi-release-2.0.0-1.sl5.noarch.rpm EMI 2 repos - please install this emi-release-2.0.0-1.sl6.noarch.rpm
EGI trust anchors repo - egi-trustanchors.repo EGI trust anchors repo - egi-trustanchors.repo EGI trust anchors repo - egi-trustanchors.repo
 
IGI (1) repo - igi-emi.repo IGI (2) repo igi-emi2.repo IGI (2) repo - igi-emi2.repo

It is strongly recommended the use of the lastest version of the emi-release packages mentioned above as they containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL.

Revision 572012-10-16 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 36 to 36
  If you don't find useful information in this documentation please have also a look to the official EMI documentation:
Changed:
<
<
>
>
 
Added:
>
>
 

Repository Settings

Line: 48 to 49
 If not present by default on your SL6/x86_64 nodes, you should enable the EPEL repository (https://fedoraproject.org/wiki/EPEL)

EPEL has an epel-release package that includes the gpg key used for package signing and other repository information, like the .repo files.

Changed:
<
<
For SL5/x86_64 installing this package, http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm, should allow you to use normal tools such as yum to install packages and their dependencies. For SL6/x86_64 installing this package, http://ftp-stud.hs-esslingen.de/pub/epel//6/x86_64/epel-release-6-7.noarch.rpm
>
>
Tto use normal tools such as yum to install packages and their dependencies
 
Changed:
<
<
By default the stable EPEL repo is enabled. Example of epel.repo file:
>
>
By default the stable EPEL repo is enabled. Example of epel-5.repo file:
 
[extras]
name=epel
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch

Line: 61 to 63
 IMPORTANT NOTE:
  • If present remember to disable the dag.repo if it is enabled.
Changed:
<
<
You need to have enabled only the following repositories (Operating System, EPEL, Certification Authority, EMI):
>
>
You need to have enabled only the following repositories: Operating System, EPEL, Certification Authority, EMI, IGI. Please see the table bellow for details:
 
SL5 x86_64 SL6 x86_64
EMI1 EMI2 EMI2
Changed:
<
<
epel.repo
Please install this rpm
epel.repo
Please install this rpm
epel.repo
Please install this rpm
emi.repo
(emi1-base.repo emi1-third-party.repo emi1-updates.repo)
Please install this rpm
emi.repo
(emi2-base.repo emi2-third-party.repo emi2-updates.repo)
Please install this rpm
emi.repo
(emi2-base.repo emi2-third-party.repo emi2-updates.repo)
Please install this rpm
>
>
epel-5.repo - please install epel-release-5-4.noarch.rpm epel-5.repo - please install epel-release-5-4.noarch.rpm epel-6.repo - please install epel-release-6-7.noarch.rpm
EMI 1 repos - emi1-base.repo, emi1-updates.repo, emi1-third-party.repo
Please install emi-release-1.0.1-1.sl5.noarch.rpm
EMI 2 repos - emi2-base.repo, emi2-updates.repo, emi2-third-party.repo
Please install emi-release-2.0.0-1.sl5.noarch.rpm
EMI 2 repos - emi2-base.repo, emi2-updates.repo, emi2-third-party.repo
Please install this emi-release-2.0.0-1.sl6.noarch.rpm
 
egi-trustanchors.repo egi-trustanchors.repo egi-trustanchors.repo
Changed:
<
<
igi-emi.repo igi-emi2.repo igi-emi2.repo

It is strongly recommended the use of the lastest version of the emi-release 1

>
>
IGI (1) repo - igi-emi.repo IGI (2) repo igi-emi2.repo IGI (2) repo - igi-emi2.repo
 
Changed:
<
<
package containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL:
>
>
It is strongly recommended the use of the lastest version of the emi-release packages mentioned above as they containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL. Example:for EMI 1 case
 

Added:
>
>
# rpm --import http://emisoft.web.cern.ch/emisoft/dist/EMI/1/RPM-GPG-KEY-emi
 # wget http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm # yum localinstall emi-release-1.0.1-1.sl5.noarch.rpm

Revision 562012-10-16 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 944 to 944
 

HLR Server Installation and Configuration

Deleted:
<
<
Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:

# yum clean all
 

HLR Prerequisites

Hardware Requirements

Changed:
<
<
The HLR server host should be an real or virtual host having an optimal disk access.
>
>
The HLR server host should be a real or virtual node having an optimal disk access.
  The suggested requirements are:
Changed:
<
<
  • processor with 4 or 8 cores
  • 8GB RAM or better 16GB
>
>
  • 4/8 cores CPU
  • 8/16GB RAM
 
  • minimum 200 GB of space for a first level HLR. (if you have an old HLR server please check your database actual dimension and redouble the partition size)
Changed:
<
<
>
>

Co-Hosting

Due to the critical nature the HLR server should be installed as a stand-alone service.

Virtual vs. Physical

 If you will use a virtual host ensure you are not using virtio to access to the mysql storage DB. Please use a physical partition.

Host certificate installation:

Line: 985 to 980
 [~]# chmod 0600 hostcert.pem
Changed:
<
<

CAs installation:

>
>

Middleware Installation

Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:

# yum clean all

CAs installation:

 
  • Install CAs on ALL profiles:
# yum install ca-policy-egi-core
Changed:
<
<

Service installation

>
>

HLR Server installation

 
  • Have a look to the HLR documentation before starting the installation: Service Guide.
  • Install the HLR metapackages, containing all packages needed:
Line: 999 to 1003
 # yum install igi-hlr;
Changed:
<
<

Service Configuration

>
>

Middleware Configuration

 
Changed:
<
<

YAIM Verification

>
>

Verification

 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the HLR profile
Line: 1009 to 1013
  If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.
Changed:
<
<

YAIM Configuration

>
>

HLR Server Configuration

 
  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
Line: 1018 to 1022
 

Post installation and configuration

Changed:
<
<
After the installation and configuration of the HLR Server Services, you should register all the resources of the CE attached to your HLR Server. Please use this command below for each CE:
>
>
After the installation and configuration of the HLR Server services, you should register all the resources of the CEs attached to your HLR Server. Please use this command below for each CE:
 
# dgas-hlr-addadmin -Sa  <CE_DN>

Revision 552012-10-15 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 45 to 45
  If not present by default on your SL5/x86_64 nodes, you should enable the EPEL repository (https://fedoraproject.org/wiki/EPEL)
Changed:
<
<
EPEL has an epel-release package that includes the gpg key used for package signing and other repository information, like the .repo files. Installing this package, http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm, should allow you to use normal tools such as yum to install packages and their dependencies. By default the stable EPEL repo is enabled. Example of epel.repo file:
>
>
If not present by default on your SL6/x86_64 nodes, you should enable the EPEL repository (https://fedoraproject.org/wiki/EPEL)

EPEL has an epel-release package that includes the gpg key used for package signing and other repository information, like the .repo files.
For SL5/x86_64 installing this package, http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm, should allow you to use normal tools such as yum to install packages and their dependencies. For SL6/x86_64 installing this package, http://ftp-stud.hs-esslingen.de/pub/epel//6/x86_64/epel-release-6-7.noarch.rpm

By default the stable EPEL repo is enabled. Example of epel.repo file:

 
[extras]
name=epel
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch

Line: 56 to 62
 
  • If present remember to disable the dag.repo if it is enabled.

You need to have enabled only the following repositories (Operating System, EPEL, Certification Authority, EMI):

Changed:
<
<
Common repositories *x86_64*
epel.repo
emi.repo
(emi1-base.repo emi1-third-party.repo emi1-updates.repo)
egi-trustanchors.repo
igi-emi.repo
>
>
SL5 x86_64 SL6 x86_64
EMI1 EMI2 EMI2
epel.repo
Please install this rpm
epel.repo
Please install this rpm
epel.repo
Please install this rpm
emi.repo
(emi1-base.repo emi1-third-party.repo emi1-updates.repo)
Please install this rpm
emi.repo
(emi2-base.repo emi2-third-party.repo emi2-updates.repo)
Please install this rpm
emi.repo
(emi2-base.repo emi2-third-party.repo emi2-updates.repo)
Please install this rpm
egi-trustanchors.repo egi-trustanchors.repo egi-trustanchors.repo
igi-emi.repo igi-emi2.repo igi-emi2.repo
  It is strongly recommended the use of the lastest version of the emi-release 1

package containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL:


Changed:
<
<
# yum install yum-priorities yum-protectbase # rpm -ivh http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
>
>
# wget http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm # yum localinstall emi-release-1.0.1-1.sl5.noarch.rpm
 
Deleted:
<
<

EMI 2 repos file:

Common repositories SL5 *x86_64*
epel.repo
emi.repo
(emi2-base.repo emi2-contrib.repo emi2-third-party.repo emi2-updates.repo)
egi-trustanchors.repo
igi-emi.repo

It is strongly recommended the use of the lastest version of the emi-release 2

 

Updating from EMI 1 to EMI 2

For the update to EMI 2 you have to uninstall the old emi-release package and install the new one:

Line: 562 to 558
 If you use DGAS to account data remember to install also DGAS sensors. You can found more documentation to DGAS sensors guide


Changed:
<
<
yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers yaim-dgas
>
>
yum install igi-dgas_sensors
 

Service Configuration

Line: 945 to 941
 
Added:
>
>

HLR Server Installation and Configuration

Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:

# yum clean all

HLR Prerequisites

Hardware Requirements

The HLR server host should be an real or virtual host having an optimal disk access.

The suggested requirements are:

  • processor with 4 or 8 cores
  • 8GB RAM or better 16GB
  • minimum 200 GB of space for a first level HLR. (if you have an old HLR server please check your database actual dimension and redouble the partition size)

If you will use a virtual host ensure you are not using virtio to access to the mysql storage DB. Please use a physical partition.

Host certificate installation:

The HLR host must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:

Check existence

[~]# ls -l /etc/grid-security/hostkey.pem
-r-------- 1 root root 887 Mar 1 17:08 /etc/grid-security/hostkey.pem
[~]# ls -l /etc/grid-security/hostcert.pem
-rw-r--r-- 1 root root 1440 Mar 1 17:08 /etc/grid-security/hostcert.pem

Check expiration

[~]# openssl x509 -in hostcert.pem -noout -dates

Change permission: (if needed)

[~]# chmod 0400 hostkey.pem
[~]# chmod 0600 hostcert.pem

CAs installation:

  • Install CAs on ALL profiles:
# yum install ca-policy-egi-core

Service installation

  • Have a look to the HLR documentation before starting the installation: Service Guide.
  • Install the HLR metapackages, containing all packages needed:
# yum install igi-hlr;

Service Configuration

YAIM Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the HLR profile

# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  HLR 

If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.

YAIM Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.

 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  HLR 2>&1 | tee /root/conf_igi-HLR.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log

Post installation and configuration

After the installation and configuration of the HLR Server Services, you should register all the resources of the CE attached to your HLR Server. Please use this command below for each CE:

# dgas-hlr-addadmin -Sa  <CE_DN>

Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"

Update From previous release:

Back up the old databases :

Form previous HLR Server stop the dgas services and make a dump of the databases:

Stop the services :

# /etc/init.d/glite-dgas-hlrd stop

Check disk space Ensure you have enough space in the disk:

# df -h
You should have the space to contain the hlr and hlr_tmp database dump. (Mount an external partition or NFS partition if you don't have enough free space)

Make the dump :

mysqldump --user=root --password hlr_Padova > /data/hlr.sql
mysqldump --user=root --password hlr_tmp_Padova > /data/hlr_tmp.sql

Installation : Install again the host with SL5 x86_64 SL distribution or install a new host where the HLR Server will be installed.

Following the above instructions install the HLR Server and configure using yaim.

Stop the HLR server process:

# /etc/init.d/dgas-hlrd stop

Restore the dump :

# mysql -u root -p hlr_tmp < /data/hlr_tmp.sql
# mysql -u root -p hlr < /data/hlr.sql

execute translate DB

]# nohup /usr/sbin/dgas-hlr-translatedb --D &

Start dgas services :

# /etc/init.d/dgas-hlrd start

Execute populateJobTransSummary:

The new HLR version need to polulate the JobTransSummary

# /usr/sbin/dgas-hlr-populateJobTransSummary

Restart dgas services :

# /etc/init.d/dgas-hlrd restart

Post Update Procedure

After the update of the HLR Server Services, you should register again all the resources of the CE attached to your HLR Server. Please use this command below for each CE:

# dgas-hlr-addadmin -Sa  <CE_DN>

Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"

HLR Documentation References:

 
META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 542012-10-01 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Revision 532012-09-03 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 679 to 679
 
  • Have a look to the WN documentation before starting the installationl: WN Guide.
  • Install the WN metapackages, containing all packages needed:

Changed:
<
<
# yum install <metapackage>
>
>
# yum install <metapackage&gt emi-version;
 
  • IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of these (see table bellow)
    • IGI customizations:

Revision 522012-07-31 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 163 to 163
 
# yum install emi-bdii-site 

Deleted:
<
<
  • It's strongly recommended to install this openldap2.4 server to avoid frequent bdii crashes:
# yum install openldap2.4-servers

 

Service Configuration

To proper configure the BDII site profile you have to customize this file with you site parameter:

Line: 178 to 172
 If you would like to cutomize the BDII_site service you can modify the variables in the service-specific file in the services/ directory. You will find an example in:
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site
Deleted:
<
<
  • Remember to add the following variables to your site-info.def yaim configuration file and re-run yaim if you installed the openldap2.4-servers as recommended.

SLAPD=/usr/sbin/slapd2.4

 

YAIM Verification

Revision 512012-07-25 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 284 to 284
 

IMPORTANT NOTES:

Changed:
<
<
  • StoRM Backend v. 1.8.2.2 (EMI 1) - If the Storage Area root of a Storage Area residing on a GPFS filesystem is specified as link pointing to the real directory and the link resides on a non GPFS filesystem a sanity check at bootstrap will fail preventing the service to start.
>
>
  • StoRM Backend v. 1.8.2.2 (EMI 1) - If the Storage Area root of a Storage Area residing on a GPFS filesystem is specified as link pointing to the real directory and the link resides on a non GPFS filesystem a sanity check at bootstrap will fail preventing the service to start.
 
    • As a workaround the user can modify the definition of the Storage Area root to the real directory path rather than the link
Changed:
<
<
  • StoRM Backend v. 1.9.0 (EMI 2): - Due to a Known Issue on StoRM backend this release is not suited for GPFS installations.
  • YAIM-STORM v, 4.2.1-3 - Starting from this release the XFS file system is managed by StoRM as a standard POSIX file system. All StoRM installations on XFS file system from this release on must specify at YAIM configuration time "posixfs" as file system type. See StoRM System Administration Guide 1.3.3 for more details.
    • Description: Specifying at YAIM configuration time "xfs" as file system type will produce an invalid namespace.xml preventing BackEnd service to boot.
>
>
  • StoRM Backend v. 1.9.0 (EMI 2): - Due to a Known Issue on StoRM backend this release is not suited for GPFS installations.
  • YAIM-STORM v, 4.2.1-3 - Starting from this release the XFS file system is managed by StoRM as a standard POSIX file system. All StoRM installations on XFS file system from this release on must specify at YAIM configuration time "posixfs" as file system type. See StoRM System Administration Guide 1.3.3 for more details.
    • Description: Specifying at YAIM configuration time "xfs" as file system type will produce an invalid namespace.xml preventing BackEnd service to boot.
 
      • As workaround XFS users have to specify "posixfs" as file system type.
Line: 398 to 398
 

Service installation

Deleted:
<
<
VERY IMPORTANT NOTE:
On 18/02/2012 the EPEL 5 repository has been updated with Globus 5.2 packages. PLEASE have a look at Globus 5.2 Issues and temporary workaround
  * Install the StoRM metapackages, containing all packages needed by these four services. You can install StoRM in one host or in more hosts. The mandatory profiles to install are emi-storm-backend-mp, emi-storm-frontend-mp and emi-storm-globus-gridftp-mp. The other profiles are optional, have a look to the StoRM documentation System Administrator Guide to determinate if you need also emi-storm-gridhttps-mp or checksum.

The most common installation using one host:

Line: 422 to 416
 

YAIM Verification

Changed:
<
<
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the StoRM profiles.
>
>
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the StoRM profiles.
 
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  se_storm_backend -n se_storm_frontend -n se_storm_gridftp
 

Revision 502012-07-24 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 131 to 131
 

NTP Configuration

Check if the NTP is installed in your O.S.

Changed:
<
<
In the repo igi-emi.repo is present a rpm called yaim-addons. Please install it:
>
>
If you have installed the middleware, and you have the package glite-yaim-core in your host you have to get the repo igi-emi.repo and inside it there is a rpm called yaim-addons. Please install it:
 
wget http://repo-pd.italiangrid.it/mrepo/repos/igi/sl5/x86_64/igi-emi.repo

Revision 492012-07-03 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 109 to 109
 
File or Directory Scope Example Details
<your-site-info.def> whole-site ig-site-info.def 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>.
Changed:
<
<
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
>
>
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
 
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful

Known issues

Revision 482012-06-22 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 283 to 283
 
yum clean all
Added:
>
>
IMPORTANT NOTES:
  • StoRM Backend v. 1.8.2.2 (EMI 1) - If the Storage Area root of a Storage Area residing on a GPFS filesystem is specified as link pointing to the real directory and the link resides on a non GPFS filesystem a sanity check at bootstrap will fail preventing the service to start.
    • As a workaround the user can modify the definition of the Storage Area root to the real directory path rather than the link
  • StoRM Backend v. 1.9.0 (EMI 2): - Due to a Known Issue on StoRM backend this release is not suited for GPFS installations.
  • YAIM-STORM v, 4.2.1-3 - Starting from this release the XFS file system is managed by StoRM as a standard POSIX file system. All StoRM installations on XFS file system from this release on must specify at YAIM configuration time "posixfs" as file system type. See StoRM System Administration Guide 1.3.3 for more details.
    • Description: Specifying at YAIM configuration time "xfs" as file system type will produce an invalid namespace.xml preventing BackEnd service to boot.
      • As workaround XFS users have to specify "posixfs" as file system type.
 

StoRM Prerequisites

Host certificate installation:

Revision 472012-06-07 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 101 to 101
 Tips & Tricks:
Deleted:
<
<

Globus 5.2 Issues and temporary workaround

due to backward incompatible changes present in the latest versions of some Globus 5.2 packages, distributed through EPEL 5 repositories, EMI services can have problems if the nodes running these services are configured to receive automatic updates or on fresh installations.

As a fast workaround, until the issues are solved on IGE/EPEL side, the Globus 5.0.3 packages are now temporary available through the EMI third-party repository.

Sites that have automatic updates enabled and have observed problems in services due to the Globus ugrade should downgrade the globus-* packages by doing:

# yum clean all
# yum downgrade globus\*

EMI DPM and StoRM-GridFTP-Server are, as of today, the EMI Services known to have problems with the Globus upgrade.

After downgrading the packages, restart the services. Also the gridftp server instances need to be restarted using the following commands:

  • EMI Disk Pool Manager (DPM)
# /etc/init.d/dpm-gsiftp restart
 # service storm-globus-gridftp restart 
 

Generic Configuration

Configuration files

IGI YAIM configuration files

Revision 462012-06-01 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 32 to 32
  ... and then reboot the system.
Added:
>
>

EMI release useful link

If you don't find useful information in this documentation please have also a look to the official EMI documentation: * EMI 1 product pages * EMI 1 update pages * EMI 2 product pages

 

Repository Settings

To have more details to the repository have a look to the this link Repository Specifications

Line: 56 to 63
 
egi-trustanchors.repo
igi-emi.repo
Changed:
<
<
It is strongly recommended the use of the lastest version of the emi-release package containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL:
>
>
It is strongly recommended the use of the lastest version of the emi-release 1

package containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL:

 
# yum install yum-priorities yum-protectbase
# rpm -ivh http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
Added:
>
>

EMI 2 repos file:

Common repositories SL5 *x86_64*
epel.repo
emi.repo
(emi2-base.repo emi2-contrib.repo emi2-third-party.repo emi2-updates.repo)
egi-trustanchors.repo
igi-emi.repo

It is strongly recommended the use of the lastest version of the emi-release 2

Updating from EMI 1 to EMI 2

For the update to EMI 2 you have to uninstall the old emi-release package and install the new one:

# rpm -e emi-release
# rpm -ivh http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl5/x86_64/base/emi-release-2.0.0-1.sl5.noarch.rpm
 

Important note on automatic updates

Several site use auto update mechanism. Sometimes middleware updates require non-trivial configuration changes or a reconfiguration of the service. This could involve service restarts, new configuration files, etc, which makes it difficult to ensure that automatic updates will not break a service. Thus

Revision 452012-04-20 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 101 to 101
 
File or Directory Scope Example Details
<your-site-info.def> whole-site ig-site-info.def 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>.
Changed:
<
<
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
>
>
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
 
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful

Known issues

Revision 442012-04-19 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 98 to 98
 

IGI 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:

Changed:
<
<
File Scope Example Details
>
>
File or Directory Scope Example Details
 
<your-site-info.def> whole-site ig-site-info.def 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>.
Changed:
<
<
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
>
>
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
<vo.d> whole-site vo.d In this directory shuld be the VO name files containing the VO configuration
It's not a mandatory directory. bus should be useful
  Known issues
  • BDII_DELETE_DELAY default value is missing for services other than BDII site & top.

Revision 432012-03-20 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 101 to 101
 
File Scope Example Details
<your-site-info.def> whole-site ig-site-info.def 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>.
Changed:
<
<
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
>
>
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
  Known issues
  • BDII_DELETE_DELAY default value is missing for services other than BDII site & top.

Revision 422012-03-19 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 119 to 119
  The optional folders are created to allow system administrators to organise their configurations in a more structured way.”
Added:
>
>

NTP Configuration

Check if the NTP is installed in your O.S.
In the repo igi-emi.repo is present a rpm called yaim-addons. Please install it:

wget http://repo-pd.italiangrid.it/mrepo/repos/igi/sl5/x86_64/igi-emi.repo
yum install yaim-addons

After that you can use yaim to configure ntrp:

/opt/glite/yaim/bin/yaim -r -d 6 -s <site-info.def> -n <node_type> -f config_ntp
 

BDII Site installation and Configuration

Have a look to the section Repository Settings of this documentation and ensure to have the common .repo files.

Line: 371 to 386
 
On 18/02/2012 the EPEL 5 repository has been updated with Globus 5.2 packages. PLEASE have a look at Globus 5.2 Issues and temporary workaround
Changed:
<
<
  • Install the StoRM metapackages, containing all packages needed by these four services. You can install StoRM in one host or in more hosts. The mandatory profiles to install are emi-storm-backend-mp and emi-storm-frontend-mp. The other profiles are optional, have a look to the StoRM documentation System Administrator Guide to determinate if you need also emi-storm-globus-gridftp-mp or emi-storm-gridhttps-mp.
>
>
* Install the StoRM metapackages, containing all packages needed by these four services. You can install StoRM in one host or in more hosts. The mandatory profiles to install are emi-storm-backend-mp, emi-storm-frontend-mp and emi-storm-globus-gridftp-mp. The other profiles are optional, have a look to the StoRM documentation System Administrator Guide to determinate if you need also emi-storm-gridhttps-mp or checksum.

The most common installation using one host:

 
yum install emi-storm-backend-mp
yum install emi-storm-frontend-mp
yum install emi-storm-globus-gridftp-mp

Deleted:
<
<
yum install emi-storm-gridhttps-mp
 

Service Configuration

Revision 412012-03-07 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 833 to 833
 
# yum install glite-mpi 
  • WNs also require a working MPI implementation, Open MPI and MPICH-2 are recommended. The devel packages should also be installed in order to allow user to compile their applications. Refer to your OS repositories for the exact packages.
    • If you would like to use the OPEN MPI flavour in your site please install:
      #yum install openmpi openmpi-devel 
Changed:
<
<
    • If you would like to use the MPICH2 flavour in your site please install:
      # yum install mpich2 
>
>
    • If you would like to use the MPICH2 flavour in your site please install:
      # yum install mpich2  mpich2-devel
 
Line: 857 to 857
 
glite-mpi MPI_MPICH_ENABLE MPI_MPICH_ENABLE = "no" Support for MPICH Flavour
glite-mpi MPI_MPICH2_ENABLE MPI_MPICH2_ENABLE="yes" Support for MPICH2 Flavour
glite-mpi MPI_OPENMPI_ENABLE MPI_OPENMPI_ENABLE="yes" Support for OPENMPI Flavour
Changed:
<
<
glite-mpi MPI_MPICH2_PATH MPI_MPICH2_PATH="/usr/lib64" MPICH2 path
>
>
glite-mpi MPI_MPICH2_PATH MPI_MPICH2_PATH="/usr/lib64/mpich2/" MPICH2 path
 
glite-mpi MPI_MPICH2_VERSION MPI_MPICH2_VERSION="1.2.1p1" MPICH2 version
glite-mpi MPI_OPENMPI_PATH MPI_OPENMPI_PATH="/usr/lib64/openmpi/1.4-gcc/" OPENMPI path
glite-mpi MPI_OPENMPI_VERSION MPI_OPENMPI_VERSION="1.4-4" OPENMPI version

Revision 402012-03-05 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 70 to 70
  on the IGI/EMI middleware repositories (you can keep it turned on for the OS). You should read the update information provides by each service and do the upgrade manually when an update has been released!
Added:
>
>
Tips & Tricks:
 

Globus 5.2 Issues and temporary workaround

due to backward incompatible changes present in the latest versions of some Globus 5.2 packages, distributed through EPEL 5 repositories, EMI services can have problems if the nodes running these services are configured to receive automatic updates or on fresh installations.

Revision 392012-02-29 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 70 to 70
  on the IGI/EMI middleware repositories (you can keep it turned on for the OS). You should read the update information provides by each service and do the upgrade manually when an update has been released!
Added:
>
>

Globus 5.2 Issues and temporary workaround

due to backward incompatible changes present in the latest versions of some Globus 5.2 packages, distributed through EPEL 5 repositories, EMI services can have problems if the nodes running these services are configured to receive automatic updates or on fresh installations.

As a fast workaround, until the issues are solved on IGE/EPEL side, the Globus 5.0.3 packages are now temporary available through the EMI third-party repository.

Sites that have automatic updates enabled and have observed problems in services due to the Globus ugrade should downgrade the globus-* packages by doing:

# yum clean all
# yum downgrade globus\*

EMI DPM and StoRM-GridFTP-Server are, as of today, the EMI Services known to have problems with the Globus upgrade.

After downgrading the packages, restart the services. Also the gridftp server instances need to be restarted using the following commands:

  • EMI Disk Pool Manager (DPM)
# /etc/init.d/dpm-gsiftp restart
 # service storm-globus-gridftp restart 
 

Generic Configuration

Configuration files

IGI YAIM configuration files

Line: 81 to 101
 
<your-users.conf> whole-site ig-users.conf 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: ”<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 ig-groups.conf 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.
Added:
>
>
Known issues
  • BDII_DELETE_DELAY default value is missing for services other than BDII site & top.
    • Workaround - add to your site-info.def BDII_DELETE_DELAY=0
 

Additional files

Furthermore the configuration folder can contain:

Line: 228 to 252
  Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:
Changed:
<
<
>
>
has been updated with a Globus version higher and some profile such as StoRM and DPM has problem with this version, so please use the UMD repositories. Have a look to Repository Settings
 
yum clean all
Line: 341 to 365
 
VERY IMPORTANT NOTE:
Changed:
<
<
On 20/02/2012 the EMI repositories has been updated, with a Globus version higher and some profile such as StoRM and DPM has problem with this version, so please use the UMD repositories. Have a look to Repository Settings
>
>
On 18/02/2012 the EPEL 5 repository has been updated with Globus 5.2 packages. PLEASE have a look at Globus 5.2 Issues and temporary workaround
 

  • Install the StoRM metapackages, containing all packages needed by these four services. You can install StoRM in one host or in more hosts. The mandatory profiles to install are emi-storm-backend-mp and emi-storm-frontend-mp. The other profiles are optional, have a look to the StoRM documentation System Administrator Guide to determinate if you need also emi-storm-globus-gridftp-mp or emi-storm-gridhttps-mp.

Revision 382012-02-24 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 338 to 338
 

Service installation

Added:
>
>
VERY IMPORTANT NOTE:
On 20/02/2012 the EMI repositories has been updated, with a Globus version higher and some profile such as StoRM and DPM has problem with this version, so please use the UMD repositories. Have a look to Repository Settings
 
  • Install the StoRM metapackages, containing all packages needed by these four services. You can install StoRM in one host or in more hosts. The mandatory profiles to install are emi-storm-backend-mp and emi-storm-frontend-mp. The other profiles are optional, have a look to the StoRM documentation System Administrator Guide to determinate if you need also emi-storm-globus-gridftp-mp or emi-storm-gridhttps-mp.
yum install emi-storm-backend-mp
yum install emi-storm-frontend-mp

Revision 372012-02-24 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 716 to 716
 
Changed:
<
<
  • [[Other Documentation available here
>
>
  • Other Documentation available here
 

UI Installation and Configuration

Revision 362012-02-19 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 62 to 62
 # rpm -ivh http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
Added:
>
>

Important note on automatic updates

Several site use auto update mechanism. Sometimes middleware updates require non-trivial configuration changes or a reconfiguration of the service. This could involve service restarts, new configuration files, etc, which makes it difficult to ensure that automatic updates will not break a service. Thus

WE STRONGLY RECOMMEND NOT TO USE AUTOMATIC UPDATE PROCEDURE OF ANY KIND

on the IGI/EMI middleware repositories (you can keep it turned on for the OS). You should read the update information provides by each service and do the upgrade manually when an update has been released!

 

Generic Configuration

Configuration files

IGI YAIM configuration files

Revision 352012-02-17 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 597 to 597
 Before starting the installation procedure remember to clean all yum cache and headers:


Changed:
<
<
yum clean all
>
>
# yum clean all
 

WN Prerequisites

Line: 611 to 611
 

CAs installation:

  • Install CAs on ALL profiles:
Changed:
<
<
yum install ca-policy-egi-core

>
>
# yum install ca-policy-egi-core

 

Service installation

Line: 619 to 619
 
  • Have a look to the WN documentation before starting the installationl: WN Guide.
  • Install the WN metapackages, containing all packages needed:

Changed:
<
<
yum install <metapackage>
>
>
# yum install <metapackage>
 
  • IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of these (see table bellow)
    • IGI customizations:
Line: 659 to 659
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the WN profiles (WN_torque, WN_torque_noafs, WN_LSF, WN_LSF_noafs)

For Torque:

Changed:
<
<
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque 
>
>
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque 
 or
Changed:
<
<
 /glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque_noafs 
>
>
# /glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque_noafs 
  For LSF:
Changed:
<
<
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF
>
>
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF
 or
Changed:
<
<
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF_noafs
>
>
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF_noafs
  For Other Batch System:
Changed:
<
<
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN
>
>
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN
  You can find in this documentation: YAIM WN Variables all mandatory variables.
Line: 687 to 687
 

  • For Torque:
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 or
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 
  • For LSF:
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 or
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 
  • For Other Batch System:
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
Line: 715 to 715
 
  • Have a look to the section Repository Settings and ensure that you have the common repo files
  • Before starting the installation procedure remember to clean all yum cache and headers:

Changed:
<
<
yum clean all
>
>
# yum clean all
 

CAs installation:

  • Install CAs on ALL profiles:
Changed:
<
<
yum install ca-policy-egi-core

>
>
# yum install ca-policy-egi-core

 

Service installation

Line: 729 to 729
 
  • Install the UI metapackages, containing all packages needed.


Changed:
<
<
yum install emi-ui
>
>
# yum install emi-ui
 

Service Configuration

Line: 738 to 738
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for the UI profile
Changed:
<
<
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  UI 
>
>
 # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  UI 
  You can find in this documentation: YAIM UI Variables all mandatory variables.
Line: 769 to 769
 
  • Have a look to the section Repository Settings and ensure that you have the common repo files
  • Before starting the installation procedure remember to clean all yum cache and headers:
Changed:
<
<
yum clean all
>
>
# yum clean all 
 

MPI Service installation on CE-CREAM

Changed:
<
<
Follow the CE-CREAM installation guide before starting to follow this steps below
>
>
  • Follow the CE-CREAM installation guide to install a creamCE
  • Install the MPI metapackage. It provides mpi_start and glite-yaim-mpi for configuration
 
Changed:
<
<
yum install glite-mpi
>
>
# yum install glite-mpi 
 
IMPORTANT NOTE:
Changed:
<
<
At the moment the metapackage name has not already change from glite-mpi to emi-mpi. Please install glite-mpi also in emi cream-ce and emi or igi worker nodes
>
>
Please pay attention to the metapackage name! It is glite-mpi, NOT emi-mpi or the previous one glite-MPI_utils.
Please install glite-mpi both in the creamCE and WNs nodes (IGI/EMI flavour)
 

MPI Service installation on WN

Changed:
<
<
Follow the WN installation guide before starting to follow this steps below
>
>
  • Follow the WN installation guide
  • Install the MPI metapackage. It provides mpi_start and glite-yaim-mpi for configuration
 
Changed:
<
<
yum install glite-mpi
>
>
# yum install glite-mpi 
  • WNs also require a working MPI implementation, Open MPI and MPICH-2 are recommended. The devel packages should also be installed in order to allow user to compile their applications. Refer to your OS repositories for the exact packages.
    • If you would like to use the OPEN MPI flavour in your site please install:
      #yum install openmpi openmpi-devel 
    • If you would like to use the MPICH2 flavour in your site please install:
      # yum install mpich2 
 
IMPORTANT NOTE:
Changed:
<
<
At the moment the metapackage name has not already change from glite-mpi to emi-mpi. Please install glite-mpi also in emi cream-ce and emi or igi worker nodes
>
>
If you are using Torque remember to create the munge key, and copy it to all cluster hosts (CE, Batch Master, WNs): Munge configuration
 
Changed:
<
<
If you would like to use the OPEN MPI flavour in your site please install:
yum install openmpi openmpi-devel 

If you would like to use the MPICH2 flavour in your site please install:

yum install mpich2 

  • Have a look to the MPI documentation before starting to install: MPI Guides.

IMPORTANT NOTE:
Remember if you are using Torque to create the munge key, and copy it to all cluster hosts (CE, Batch Master, WNs): Munge configuration

Service Configuration

>
>

Service Configuration

 

Useful Variables

Changed:
<
<
Remember to copy these three files in your service directory:
  • glite-mpi
  • glite-mpi_ce
  • glite-mpi_wn

Please set properly the variables in the files in service directory. In particular customize this important values:

>
>
  • Remember to copy these three files in your services/ directory:
    • /opt/glite/yaim/examples/siteinfo/services/glite-mpi
    • /opt/glite/yaim/examples/siteinfo/services/glite-mpi_ce
    • /opt/glite/yaim/examples/siteinfo/services/glite-mpi_wn
  • Set properly the variables in the above files in services/ directory. In particular customize these important values:
 
Line: 850 to 830
 

YAIM Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for the MPI profile
Changed:
<
<
    • On CE-CREAM MPI Verification
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 

    • On WN MPI Verification
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_WN -n WN_torque_noafs 

You can find in this documentation: YAIM MPI Variables all mandatory variables.

If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing.

>
>
    • On CE-CREAM MPI Verification:
      # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 
    • On WN MPI Verification:
      # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_WN -n WN_torque_noafs 
  • You can find in the "YAIM MPI Variables" documentation information about all mandatory variables.
    • If no errors are reported during the verification you can proceed to the configuration, otherwise correct them.
 

YAIM Configuration

Line: 869 to 843
 
IMPORTANT NOTE:
Changed:
<
<
Remember to put at first position the nodetype MPI_CE or MPI_WN
>
>
When configuring with yaim remember to put first the nodetype MPI_CE or MPI_WN
 
Added:
>
>
 
    • On CE-CREAM
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def>  -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 2>&1 | tee /root/conf_EMI_CREAM_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
>
>
# /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def>  -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 2>&1 | tee /root/conf_EMI_CREAM_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
 
    • On WN
Changed:
<
<
  /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_WN -n WN_torque_noafs  2>&1 | tee /root/conf_WN_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
>
>
#  /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_WN -n WN_torque_noafs  2>&1 | tee /root/conf_WN_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
 

Check files in WN

Changed:
<
<
If in YAIM Configuration you are chose to use MPI_SSH_HOST_BASED_AUTH (well-advised) check these files:
  • /etc/ssh/sshd_config
  • /etc/ssh/shosts.equiv
>
>
  • If in YAIM Configuration step you choose to use MPI_SSH_HOST_BASED_AUTH (recommended) check these files:
    • /etc/ssh/sshd_config
    • /etc/ssh/shosts.equiv
 
Changed:
<
<
The first one sshd_config should have the follow variables set like below
>
>
  • The first one, sshd_config, should have the follow variables set like below
 
HostbasedAuthentication yes 
IgnoreUserKnownHosts yes
IgnoreRhosts yes
Changed:
<
<
The second file shosts.equiv should contains: the CE hostname, the default SE host name and all the WNs hostname. May be in the CE it was created in configuration process, copy it form the CE.

Restart sshd services after file modification:

service sshd restart
>
>
  • The second file, shosts.equiv, should contain: the CE hostname, the default SE host name and all the WNs hostname. Maybe in the CE it was created in configuration process, copy it form there to all WNs
  • Restart sshd services after file modification:
 service sshd restart
 

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to Service Reference Card and User & Service Troubleshooting Guide. In this page you can find some common errors and other useful service information.
>
>
 

MPI Documentation References:

Changed:
<
<
>
>
 

META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 342012-02-17 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 778 to 778
 Follow the CE-CREAM installation guide before starting to follow this steps below


Changed:
<
<
yum install mpi-start glite-yaim-mpi
>
>
yum install glite-mpi
 
Added:
>
>
IMPORTANT NOTE:
At the moment the metapackage name has not already change from glite-mpi to emi-mpi. Please install glite-mpi also in emi cream-ce and emi or igi worker nodes
 

MPI Service installation on WN

Follow the WN installation guide before starting to follow this steps below


Changed:
<
<
yum install mpi-start glite-yaim-mpi yum install openmpi openmpi-devel mpich2
>
>
yum install glite-mpi

IMPORTANT NOTE:
At the moment the metapackage name has not already change from glite-mpi to emi-mpi. Please install glite-mpi also in emi cream-ce and emi or igi worker nodes

If you would like to use the OPEN MPI flavour in your site please install:

yum install openmpi openmpi-devel 

If you would like to use the MPICH2 flavour in your site please install:

yum install mpich2 

 

  • Have a look to the MPI documentation before starting to install: MPI Guides.
Line: 877 to 898
 

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to User & Service Troubleshooting Guide. In this page you can find some common errors and other useful service information.
>
>
After service installation to have a look if all were installed in a proper way, you could have a look to Service Reference Card and User & Service Troubleshooting Guide. In this page you can find some common errors and other useful service information.
 

MPI Documentation References:

Changed:
<
<
>
>
 
Changed:
<
<
>
>
 
Changed:
<
<
>
>
 
META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 332012-02-16 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 137 to 137
 SITE_OTHER_EGI_NGI="NGI_IT"
Changed:
<
<
If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration.
>
>
If no errors are reported you can proceed to the configuration, otherwise correct them before continuing.
 

YAIM Configuration

Changed:
<
<
Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.
>
>
Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience you can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
 
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log

Service Testing - Reference Card

Revision 322012-02-16 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 708 to 708
 
Changed:
<
<
  • Other Documentation available here
>
>
  • [[Other Documentation available here
 

UI Installation and Configuration

Line: 764 to 764
 
Added:
>
>

MPI Installation and Configuration

  • Have a look to the section Repository Settings and ensure that you have the common repo files
  • Before starting the installation procedure remember to clean all yum cache and headers:
yum clean all

MPI Service installation on CE-CREAM

Follow the CE-CREAM installation guide before starting to follow this steps below

yum install mpi-start glite-yaim-mpi

MPI Service installation on WN

Follow the WN installation guide before starting to follow this steps below

yum install mpi-start glite-yaim-mpi
yum install openmpi openmpi-devel mpich2

  • Have a look to the MPI documentation before starting to install: MPI Guides.

IMPORTANT NOTE:
Remember if you are using Torque to create the munge key, and copy it to all cluster hosts (CE, Batch Master, WNs): Munge configuration

Service Configuration

Useful Variables

Remember to copy these three files in your service directory:

  • glite-mpi
  • glite-mpi_ce
  • glite-mpi_wn

Please set properly the variables in the files in service directory. In particular customize this important values:

File name Variable common value Description
glite-mpi MPI_MPICH_ENABLE MPI_MPICH_ENABLE = "no" Support for MPICH Flavour
glite-mpi MPI_MPICH2_ENABLE MPI_MPICH2_ENABLE="yes" Support for MPICH2 Flavour
glite-mpi MPI_OPENMPI_ENABLE MPI_OPENMPI_ENABLE="yes" Support for OPENMPI Flavour
glite-mpi MPI_MPICH2_PATH MPI_MPICH2_PATH="/usr/lib64" MPICH2 path
glite-mpi MPI_MPICH2_VERSION MPI_MPICH2_VERSION="1.2.1p1" MPICH2 version
glite-mpi MPI_OPENMPI_PATH MPI_OPENMPI_PATH="/usr/lib64/openmpi/1.4-gcc/" OPENMPI path
glite-mpi MPI_OPENMPI_VERSION MPI_OPENMPI_VERSION="1.4-4" OPENMPI version
glite-mpi MPI_MPICH_MPIEXEC MPI_MPICH_MPIEXEC="/usr/bin/mpiexec" MPICH MPIEXEC path
glite-mpi MPI_MPICH2_MPIEXEC MPI_MPICH2_MPIEXEC="/usr/bin/mpiexec" MPICH2 MPIEXEC path
glite-mpi MPI_OPENMPI_MPIEXEC MPI_OPENMPI_MPIEXEC="/usr/lib64/openmpi/1.4-gcc/bin/mpiexec" OPENMPI MPIEXEC path
glite-mpi MPI_SSH_HOST_BASED_AUTH MPI_SSH_HOST_BASED_AUTH=${MPI_SSH_HOST_BASED_AUTH:-"yes"} Use the SSH Hostbased Authentication between your WNs
glite-mpi_ce MPI_SUBMIT_FILTER MPI_SUBMIT_FILTER=${MPI_SUBMIT_FILTER:-"yes"} For Torque ensure that CPU allocation is performed correctly

YAIM Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for the MPI profile

    • On CE-CREAM MPI Verification
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 

    • On WN MPI Verification
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_WN -n WN_torque_noafs 

You can find in this documentation: YAIM MPI Variables all mandatory variables.

If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing.

YAIM Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.

IMPORTANT NOTE:
Remember to put at first position the nodetype MPI_CE or MPI_WN
    • On CE-CREAM
 /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def>  -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 2>&1 | tee /root/conf_EMI_CREAM_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
    • On WN
  /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_WN -n WN_torque_noafs  2>&1 | tee /root/conf_WN_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 

Check files in WN

If in YAIM Configuration you are chose to use MPI_SSH_HOST_BASED_AUTH (well-advised) check these files:

  • /etc/ssh/sshd_config
  • /etc/ssh/shosts.equiv

The first one sshd_config should have the follow variables set like below

HostbasedAuthentication yes 
IgnoreUserKnownHosts yes
IgnoreRhosts yes

The second file shosts.equiv should contains: the CE hostname, the default SE host name and all the WNs hostname. May be in the CE it was created in configuration process, copy it form the CE.

Restart sshd services after file modification:

service sshd restart

Service Testing - Reference Card

After service installation to have a look if all were installed in a proper way, you could have a look to User & Service Troubleshooting Guide. In this page you can find some common errors and other useful service information.

MPI Documentation References:

 
META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 312012-02-10 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 591 to 591
 
Changed:
<
<

WN Installation and Configuration - WORK IN PROGRESS

>
>

WN Installation and Configuration

  Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:
Line: 616 to 616
 

Service installation

Changed:
<
<
Install the WN metapackages, containing all packages needed. Have a look to the WN documentation before starting to install: WN Guides. IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of theese:
>
>
  • Have a look to the WN documentation before starting the installationl: WN Guide.
  • Install the WN metapackages, containing all packages needed:
yum install <metapackage>
  • IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of these (see table bellow)
    • IGI customizations:
      • unique metapackages & configurations for WNs with support for the batch systems Torque & LSF
      • contains the "LCG Applications Dependency Metapackage" - HEP_OSLib, compat-gcc-34-g77, compat-libgcc-296, compat-libstdc++-296, gcc-c++, ghostscript lapack, ncurses, openafs, openafs-client, openldap-clients
      • contains yaim-addons - new configuration package with IGI-custom configuration functions and files (replaces ig-yaim)
 
Profiles Metapackages INSTALLATION Nodetypes CONFIGURATION
WN igi-wn
igi-wn_lsf
igi-wn_lsf_noafs
igi-wn_torque
igi-wn_torque_noafs
WN
WN_LSF
WN_LSF_noafs
WN_torque
WN_torque_noafs
Changed:
<
<
Note: the igi-wn metapackage is useful for SGE or other Batch System

yum install <metapackage>
>
>
Note: the igi-wn metapackage is useful for SGE or other Batch System
 
IMPORTANT NOTE:
Changed:
<
<
All the metapackages name are case sensitive, you have to write it as described above.
>
>
Name are case sensitive, both for metapackages installation and notetype configuration, you have to use the ones in the table above.
 
Deleted:
<
<
IMPORTANT NOTE FOR TORQUE: After the Torque installation you should have the version 2.5.7-7. Please remember to copy the munge key from the batch master to the WN just installed
scp <batch master host>:/etc/munge/munge.key /etc/munge
 
Added:
>
>
IMPORTANT NOTE FOR TORQUE:
After the Torque installation you should have the version 2.5.7-7.
Please remember to copy the munge key from the batch master to the WN just installed
# scp <batch master host>:/etc/munge/munge.key /etc/munge 
 

Service Configuration

Line: 664 to 673
  You can find in this documentation: YAIM WN Variables all mandatory variables.
Changed:
<
<
If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration.
>
>
If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.
 

YAIM Configuration

Changed:
<
<
Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
>
>
  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
 
Line: 676 to 686
 
All the nodetypes name are case sensitive, you have to write it as described above.
Changed:
<
<
For Torque:
>
>
  • For Torque:
 
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
or
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
Changed:
<
<
For LSF:
>
>
  • For LSF:
 
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
or
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
Changed:
<
<
For Other Batch System:
>
>
  • For Other Batch System:
 
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information.
>
>
After service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information.
 

WN Documentation References:

Changed:
<
<
>
>
 
  • Other Documentation available here
Added:
>
>

UI Installation and Configuration

 
Changed:
<
<

UI Installation and Configuration - WORK IN PROGRESS

Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:

>
>
  • Have a look to the section Repository Settings and ensure that you have the common repo files
  • Before starting the installation procedure remember to clean all yum cache and headers:
 
yum clean all
Line: 718 to 725
 

Service installation

Changed:
<
<
Install the UI metapackages, containing all packages needed. Have a look to the UI documentation before starting to install: UI Guides.
>
>
  • Have a look to the UI documentation before starting to install: UI Guides.
  • Install the UI metapackages, containing all packages needed.
 
yum install emi-ui

Line: 729 to 736
 

YAIM Verification

Changed:
<
<
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the UI profile
>
>
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for the UI profile
 
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  UI 

You can find in this documentation: YAIM UI Variables all mandatory variables.

Changed:
<
<
If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration.
>
>
If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing.
 

YAIM Configuration

Changed:
<
<
Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
>
>
  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
 
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can found some typical problems occured and any other useful service information.
>
>
After service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can find some commonl errors and other useful service information.
 

UI Documentation References:

Changed:
<
<
>
>
 
META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 302012-02-10 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 142 to 142
 

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.

Changed:
<
<
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
>
>
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

Service Testing - Reference Card

Line: 192 to 192
 

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.

Changed:
<
<
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
>
>
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

Know Issue and Workaround

Line: 366 to 366
  Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
Changed:
<
<
# /opt/glite/yaim/bin/yaim -c -d 6 -s -n  se_storm_backend -n se_storm_frontend -n se_storm_gridftp 2>&1 | tee /root/conf_StroRM_BE_FE_Gftp.`hostname -s`.`date`.log
>
>
# /opt/glite/yaim/bin/yaim -c -d 6 -s -n  se_storm_backend -n se_storm_frontend -n se_storm_gridftp 2>&1 | tee /root/conf_StroRM_BE_FE_Gftp.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
  IMPORTANT NOTE The order of the profile is important and must be : -n se_storm_backend -n se_storm_frontend
Line: 564 to 564
 

For Torque:

Changed:
<
<
# /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_Torque_DGAS.`hostname -s`.`date`.log
>
>
# /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_Torque_DGAS.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
  For LSF:
Changed:
<
<
# /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  creamCE -n LSF_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_LSF_DGAS.`hostname -s`.`date`.log
>
>
# /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  creamCE -n LSF_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_LSF_DGAS.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

Service Testing - Reference Card

Line: 677 to 677
 

For Torque:

Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date`.log
>
>
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 or
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date`.log
>
>
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
  For LSF:
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date`.log
>
>
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 or
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date`.log
>
>
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
  For Other Batch System:
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date`.log
>
>
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

Service Testing - Reference Card

Line: 742 to 742
 Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date`.log
>
>
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

Service Testing - Reference Card

Revision 292012-02-09 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 76 to 76
 

Additional files

Furthermore the configuration folder can contain:

Changed:
<
<
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.
>
>
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.”
Line: 176 to 176
  To proper configure the BDII top profile you have to customize this file with you site parameter:
Changed:
<
<
- ig-site-info.def
>
>
 

YAIM Verification

Line: 341 to 341
  To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter:
Changed:
<
<
- ig-site-info.def
- ig-users.conf
- ig-groups.conf
>
>
 

YAIM Verification

Line: 402 to 402
 

Host certificate installation:

Changed:
<
<
All nodes except UI, WN and BDII require the host certificate/key files to be installed. Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.
>
>
All nodes except UI, WN and BDII require the host certificate/key files to be installed.
Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.
  Once you have obtained a valid certificate:
Line: 466 to 467
 yum install emi-torque-utils
Changed:
<
<
* If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage:
>
>
  • If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage:
 
yum install emi-torque-utils

Line: 549 to 550
 USE_ARGUS=no
Changed:
<
<
DGAS_sensors:
>
>
DGAS_sensors:
 For DGAS_sensors you should customize the services file. You can find in this path an example:
/opt/glite/yaim/examples/siteinfo/services/dgas_sensors 
Deleted:
<
<
 

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.

Line: 618 to 618
  Install the WN metapackages, containing all packages needed. Have a look to the WN documentation before starting to install: WN Guides. IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of theese:
Changed:
<
<
  • igi-wn_torque
  • igi-wn_torque_noafs
  • igi-wn_lsf
  • igi-wn_lsf_noafs
  • igi-wn (useful for SGE or other Batch System)
>
>
Profiles Metapackages INSTALLATION Nodetypes CONFIGURATION
WN igi-wn
igi-wn_lsf
igi-wn_lsf_noafs
igi-wn_torque
igi-wn_torque_noafs
WN
WN_LSF
WN_LSF_noafs
WN_torque
WN_torque_noafs

Note: the igi-wn metapackage is useful for SGE or other Batch System

 
yum install <metapackage>
Changed:
<
<
IMPORTANT NOTE: All the metapackages name are case sensitive, you have to write it as described above.
>
>
IMPORTANT NOTE:
All the metapackages name are case sensitive, you have to write it as described above.
  IMPORTANT NOTE FOR TORQUE: After the Torque installation you should have the version 2.5.7-7. Please remember to copy the munge key from the batch master to the WN just installed
Line: 665 to 670
  Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
Changed:
<
<
IMPORTANT NOTE:
All the profiles name are case sensitive, you have to write it as described above.
>
>
IMPORTANT NOTE:
All the nodetypes name are case sensitive, you have to write it as described above.
  For Torque:
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date`.log

Revision 282012-02-09 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 591 to 591
 
Added:
>
>

WN Installation and Configuration - WORK IN PROGRESS

Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all

WN Prerequisites

Batch System:

  • If you will use LSF (licences are needed) - The server/client installation must be done manually. Have a look to Platform LSF documentation,
  • TORQUE server/client installation is done through the use of the -torque- metapackages, see bellow

CAs installation:

  • Install CAs on ALL profiles:
yum install ca-policy-egi-core

Service installation

Install the WN metapackages, containing all packages needed. Have a look to the WN documentation before starting to install: WN Guides. IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of theese:

  • igi-wn_torque
  • igi-wn_torque_noafs
  • igi-wn_lsf
  • igi-wn_lsf_noafs
  • igi-wn (useful for SGE or other Batch System)

yum install <metapackage>

IMPORTANT NOTE: All the metapackages name are case sensitive, you have to write it as described above.

IMPORTANT NOTE FOR TORQUE: After the Torque installation you should have the version 2.5.7-7. Please remember to copy the munge key from the batch master to the WN just installed

scp <batch master host>:/etc/munge/munge.key /etc/munge

Service Configuration

YAIM Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the WN profiles (WN_torque, WN_torque_noafs, WN_LSF, WN_LSF_noafs)

For Torque:

 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque 
or
 /glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque_noafs 

For LSF:

 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF
or
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF_noafs

For Other Batch System:

 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN

You can find in this documentation: YAIM WN Variables all mandatory variables.

If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration.

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.

IMPORTANT NOTE:
All the profiles name are case sensitive, you have to write it as described above.

For Torque:

 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date`.log
or
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date`.log

For LSF:

 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date`.log
or
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date`.log

For Other Batch System:

 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date`.log

Service Testing - Reference Card

After service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information.

WN Documentation References:

UI Installation and Configuration - WORK IN PROGRESS

Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all

CAs installation:

  • Install CAs on ALL profiles:
yum install ca-policy-egi-core

Service installation

Install the UI metapackages, containing all packages needed. Have a look to the UI documentation before starting to install: UI Guides.

yum install emi-ui

Service Configuration

YAIM Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the UI profile

 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  UI 

You can find in this documentation: YAIM UI Variables all mandatory variables.

If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration.

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.

 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date`.log

Service Testing - Reference Card

After service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can found some typical problems occured and any other useful service information.

UI Documentation References:

 
META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 272012-01-26 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 68 to 68
  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 Example Details
Changed:
<
<
<your-site-info.def> whole-site ig-site-info.def 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-site-info.def> whole-site ig-site-info.def 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 ig-users.conf 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: ”<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>”.
Changed:
<
<
<your-groups.conf> whole-site ig-groups.conf 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.
>
>
<your-groups.conf> whole-site ig-groups.conf 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

Revision 262012-01-20 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 571 to 571
 

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card and also to the [http://wiki.italiangrid.it/twiki/bin/view/CREAM/CreamTestWorkPlan][Service Troubleshooting Guide]]. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
>
>
After service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card and also to the Service Troubleshooting Guide. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
 

CREAM Documentation References:

Revision 252012-01-20 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 349 to 349
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the StoRM profiles.
Changed:
<
<
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  se_storm_backend -n se_storm_frontend

>
>
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  se_storm_backend -n se_storm_frontend -n se_storm_gridftp

 

You can find in this documentation: System Administrator Guide all mandatory variables. In the section GENERAL YAIM VARIABLES

Line: 366 to 366
  Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
Changed:
<
<
# /opt/glite/yaim/bin/yaim -c -d 6 -s -n  se_storm_backend -n se_storm_frontend 2>&1 | tee /root/conf_StroRM_BE_FE.`hostname -s`.`date`.log
>
>
# /opt/glite/yaim/bin/yaim -c -d 6 -s -n  se_storm_backend -n se_storm_frontend -n se_storm_gridftp 2>&1 | tee /root/conf_StroRM_BE_FE_Gftp.`hostname -s`.`date`.log
  IMPORTANT NOTE The order of the profile is important and must be : -n se_storm_backend -n se_storm_frontend

Revision 242012-01-13 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 244 to 244
  Change permission: (if needed)
[~]# chmod 0400 hostkey.pem

Changed:
<
<
[~]# chmod 0644 hostcert.pem
>
>
[~]# chmod 0600 hostcert.pem
 

ACL SUPPORT

Line: 425 to 425
  Change permission: (if needed)
[~]# chmod 0400 hostkey.pem

Changed:
<
<
[~]# chmod 0644 hostcert.pem
>
>
[~]# chmod 0600 hostcert.pem
 

Batch System:

Revision 232012-01-13 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 472 to 472
 yum install emi-torque-utils
Added:
>
>
IMPORTANT NOTE FOR TORQUE:

After the Torque installation you should have the version 2.5.7-7. Please check that munge is installed and enabled.

rpm -qa | grep munge
munge-libs-0.5.8-8.el5
munge-0.5.8-8.el5

To enable munge on your torque cluster:

  • Install the munge package (if it is not installed) on your pbs_server, submission hosts and all worker node hosts in your cluster.
  • On one host generate a key with /usr/sbin/create-munge-key
  • Copy the key, /etc/munge/munge.key to your pbs_server, submission hosts and all worker node hosts on your cluster.
    Pay attenction the ownership of that file must be:
    -r-------- 1 munge munge 1024 Jan 03 09:57 munge.key
  • Start the munge daemon on these nodes. *service munge start && chkconfig munge on*
  * If you are running LSF, install the emi-lsf-utils metapackage:
yum install emi-lsf-utils

Revision 222012-01-10 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 538 to 538
  Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
Added:
>
>
IMPORTANT NOTE:
For Torque was found an error in starting pbs_server so if you are configuring the PBS server NODE before launching yaim remember to start pbs_server:
/etc/init.d/pbs_server start
 For Torque:
# /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_Torque_DGAS.`hostname -s`.`date`.log

Revision 212012-01-10 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 54 to 54
 
epel.repo
emi.repo
(emi1-base.repo emi1-third-party.repo emi1-updates.repo)
egi-trustanchors.repo
Added:
>
>
igi-emi.repo
  It is strongly recommended the use of the lastest version of the emi-release package containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL:

Line: 481 to 482
 If you use DGAS to account data remember to install also DGAS sensors. You can found more documentation to DGAS sensors guide


Changed:
<
<
yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers

Install also yaim-dgas rpm this could be useful when you will configure DGAS_sensors

rpm -ivh http://repo-pd.italiangrid.it/mrepo/ig_sl5-x86_64/RPMS.3_2_0/yaim-dgas-5.0.0-3.noarch.rpm

>
>
yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers yaim-dgas
 

Service Configuration

Revision 202012-01-01 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 386 to 386
 
Changed:
<
<

CREAM CE installation and Configuration

>
>

CREAM CE Installation and Configuration

  Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:
Line: 394 to 394
 
yum clean all
Changed:
<
<
The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64. We remember the Toque Server and client work only if the CE and the WN is SL5 x86_64 and the MAUI version is equal in the server and client side. Please update the WN if you have an old installation.
>
>
The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64.
  • Please remember that the TORQUE Server and Client work only if the CE and the WNs are SL5 x86_64 and the MAUI version is the same in the server and client nodes. Please update the WN if you have an old installation.
 

CREAM CE Prerequisites

Host certificate installation:

Changed:
<
<
In the host were CREAM CE is intalled must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:
>
>
All nodes except UI, WN and BDII require the host certificate/key files to be installed. Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.

Once you have obtained a valid certificate:

  • hostcert.pem - containing the machine public key
  • hostkey.pem - containing the machine private key

make sure to place the two files in the target node into the /etc/grid-security directory and check the access right for hostkey.pem is only readable by root (0400) and that the public key, hostcert.pem, is readable by everybody (0644).

  Check existence

Line: 421 to 429
 

Batch System:

Changed:
<
<
If you will use LSF (licences are needed). The server/client installation must be done manually. Have a look to Platform LSF documentation, whereas Torque server/client installation is included in the Toque metapackages.
>
>
  • If you will use LSF (licences are needed) - The server/client installation must be done manually. Have a look to Platform LSF documentation,
  • TORQUE server/client installation is done through the use of the -torque- metapackages, see bellow

Access to batch system log files
It doesn't matter what kind of deployment you have, batch-system master on a different machine than the CE (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
 

CAs installation:

Line: 438 to 454
 yum install emi-cream-ce
Changed:
<
<

Batch system utility installation

>
>

Batch System Utilities installation

  After the installation of the CREAM CE metapackage it is necessary to install the batch system specific metapackage(s):
Line: 536 to 552
  After service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card and also to the [http://wiki.italiangrid.it/twiki/bin/view/CREAM/CreamTestWorkPlan][Service Troubleshooting Guide]]. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
Changed:
<
<

Documentation References:

>
>

CREAM Documentation References:

  * Functional Description
* Software Design Description
Line: 554 to 570
 
Deleted:
<
<
-- SergioTraldi - 2011-11-10
 
META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 192011-12-29 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Changed:
<
<

Installation

>
>

Common Installation

 

OS installation

Revision 182011-12-28 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 386 to 386
 
Added:
>
>

CREAM CE installation and Configuration

Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all

The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64. We remember the Toque Server and client work only if the CE and the WN is SL5 x86_64 and the MAUI version is equal in the server and client side. Please update the WN if you have an old installation.

CREAM CE Prerequisites

Host certificate installation:

In the host were CREAM CE is intalled must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:

Check existence

[~]# ls -l /etc/grid-security/hostkey.pem
-r-------- 1 root root 887 Mar 1 17:08 /etc/grid-security/hostkey.pem
[~]# ls -l /etc/grid-security/hostcert.pem
-rw-r--r-- 1 root root 1440 Mar 1 17:08 /etc/grid-security/hostcert.pem

Check expiration

[~]# openssl x509 -in hostcert.pem -noout -dates

Change permission: (if needed)

[~]# chmod 0400 hostkey.pem
[~]# chmod 0644 hostcert.pem

Batch System:

If you will use LSF (licences are needed). The server/client installation must be done manually. Have a look to Platform LSF documentation, whereas Torque server/client installation is included in the Toque metapackages.

CAs installation:

  • Install CAs on ALL profiles:
yum install ca-policy-egi-core

Service installation

* Install the CREAM CE metapackages, containing all packages needed. Have a look to the CREAM CE documentation before starting to install :System Administrator Guide.

yum install xml-commons-apis 
yum install emi-cream-ce

Batch system utility installation

After the installation of the CREAM CE metapackage it is necessary to install the batch system specific metapackage(s):

* If you are running Torque, and your CREAM CE node is the torque master, install the emi-torque-server and emi-torque-utils metapackages:

yum install emi-torque-server
yum install emi-torque-utils

* If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage:

yum install emi-torque-utils

* If you are running LSF, install the emi-lsf-utils metapackage:

yum install emi-lsf-utils

DGAS_sensors installation

If you use DGAS to account data remember to install also DGAS sensors. You can found more documentation to DGAS sensors guide

yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers

Install also yaim-dgas rpm this could be useful when you will configure DGAS_sensors

rpm -ivh http://repo-pd.italiangrid.it/mrepo/ig_sl5-x86_64/RPMS.3_2_0/yaim-dgas-5.0.0-3.noarch.rpm

Service Configuration

YAIM Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the CREAM CE profiles.

For Torque:

 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors
 

For LSF:

 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  creamCE -n LSF_utils -n DGAS_sensors
 

You can find in this documentation: YAIM CREAM CE Variables all mandatory variables.

If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration.

Configuration Suggestions:

Blparser:
We suggest to use the new Blparser runs on the CREAM CE machine and it is automatically installed when installing the CREAM CE. The configuration of the new BLAH Blparser is done when configuring the CREAM CE (i.e. it is not necessary to configure the Blparser separately from the CREAM CE).

To use the new BLAH blparser, it is just necessary to set:

BLPARSER_WITH_UPDATER_NOTIFIER=true

ARGUS:
If you have an ARGUS server installed in your site or in central site we suggest to use it. Please set the proper variables:

USE_ARGUS=yes

In this case it is also necessary to set the following yaim variables:

* ARGUS_PEPD_ENDPOINTS The endpoint of the ARGUS box (e.g."https://cream-43.pd.infn.it:8154/authz") * CREAM_PEPC_RESOURCEID The id of the CREAM CE in the ARGUS box (e.g. "http://pd.infn.it/cream-18")

If instead gJAF should be used as authorization system, yaim variable USE_ARGUS must be set in the following way:

USE_ARGUS=no

DGAS_sensors:
For DGAS_sensors you should customize the services file. You can find in this path an example:

/opt/glite/yaim/examples/siteinfo/services/dgas_sensors 

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.

For Torque:

# /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_Torque_DGAS.`hostname -s`.`date`.log

For LSF:

# /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  creamCE -n LSF_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_LSF_DGAS.`hostname -s`.`date`.log

Service Testing - Reference Card

After service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card and also to the [http://wiki.italiangrid.it/twiki/bin/view/CREAM/CreamTestWorkPlan][Service Troubleshooting Guide]]. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.

Documentation References:

* Functional Description
* Software Design Description
* User Guide
* Client Installation and Configuration
* Client Configuration Template
* Man Pages/Online Help
* User Troubleshooting Guide
* API Documentation
* Error Code Documentation
* System Administrator Guides
* Service Reference Card
* Service Troubleshooting Guide
* Other Documentation available here

 

-- SergioTraldi - 2011-11-10

Revision 172011-11-28 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 22 to 22
  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).
Changed:
<
<
>
>

Disabling SELinux

Please remember to fully disabling SELinux. Disabling will completely disable all SELinux functions including file and process labelling. In RedHat Enterprise, edit /etc/selinux/config and change the SELINUX line to SELINUX=disabled:
# disabled - No SELinux policy is loaded.
SELINUX=disabled

... and then reboot the system.

 

Repository Settings

To have more details to the repository have a look to the this link Repository Specifications

Revision 162011-11-25 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 182 to 182
 

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.

Changed:
<
<
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
>
>
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
 

Know Issue and Workaround

Revision 152011-11-22 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 8 to 11
  Install SL5 using SL5.X repository (CERN mirror) or one of the supported OS (RHEL5 clones).
Changed:
<
<
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
>
>
You may find information on official OS 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!
Line: 19 to 22
  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).
Added:
>
>
 

Repository Settings

To have more details to the repository have a look to the this link Repository Specifications

If not present by default on your SL5/x86_64 nodes, you should enable the EPEL repository (https://fedoraproject.org/wiki/EPEL)

Changed:
<
<
EPEL has an 'epel-release' package that includes gpg keys for package signing and repository information. Installing this package, http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm, should allow you to use normal tools such as yum to install packages and their dependencies. By default the stable EPEL repo is enabled. Example of epel.repo file:
>
>
EPEL has an epel-release package that includes the gpg key used for package signing and other repository information, like the .repo files. Installing this package, http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm, should allow you to use normal tools such as yum to install packages and their dependencies. By default the stable EPEL repo is enabled. Example of epel.repo file:
 
[extras]
name=epel
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch
protect=0
Changed:
<
<
IMPORTANT NOTE
>
>
IMPORTANT NOTE:
  • If present remember to disable the dag.repo if it is enabled.
 
Changed:
<
<
If present remember to disable the dag.repo if it is enabled.
>
>
You need to have enabled only the following repositories (Operating System, EPEL, Certification Authority, EMI):
 
Deleted:
<
<
You need to have enabled only the above repositories (Operating System, EPEL, Certification Authority, EMI):
 
Common repositories *x86_64*
epel.repo
Changed:
<
<
emi.repo (emi1-base.repo emi1-third-party.repo emi1-updates.repo)
>
>
emi.repo
(emi1-base.repo emi1-third-party.repo emi1-updates.repo)
 
egi-trustanchors.repo
Changed:
<
<
To install emi repo files with its gp key associated install these packages to protect the base repo files and the rpm:
yum install yum-priorities yum-protectbase
rpm -ivh http://emisoft.web.cern.ch/emisoft/dist/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
>
>
It is strongly recommended the use of the lastest version of the emi-release package containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL:
# yum install yum-priorities yum-protectbase
# rpm -ivh http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
 

Generic Configuration

Configuration files

Line: 66 to 73
 
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.”

Added:
>
>
 

BDII Site installation and Configuration

Changed:
<
<
Have a look to the section Repository Settings of this documentation, ensure to have the common repo files.
>
>
Have a look to the section Repository Settings of this documentation and ensure to have the common .repo files.
 Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all
Changed:
<
<

CAa installation:

>
>

CAs installation:

 
  • Install CAs on ALL profiles:
yum install ca-policy-egi-core

Line: 83 to 91
 

Service installation

  • Install the BDII_site metapackage, containing all packages needed by this service:
Changed:
<
<
yum install emi-bdii-site 

>
>
# yum install emi-bdii-site 

 

  • It's strongly recommended to install this openldap2.4 server to avoid frequent bdii crashes:

Changed:
<
<
yum install openldap2.4-servers
>
>
# yum install openldap2.4-servers
 

Line: 96 to 104
  To proper configure the BDII site profile you have to customize this file with you site parameter:
Changed:
<
<
- ig-site-info.def
>
>
  If you would like to cutomize the BDII_site service you can modify the variables in the service-specific file in the services/ directory. You will find an example in:
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site
Line: 106 to 114
 SLAPD=/usr/sbin/slapd2.4

YAIM Verification

Deleted:
<
<
Certificate will not expire.
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site 
Line: 131 to 138
  After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_site Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
Added:
>
>

Documentation References:

 

BDII Top installation and Configuration

Have a look to the section Repository Settings of this documentation, ensure to have the common repo files.

Line: 191 to 202
  After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
Added:
>
>

Documentation References:

 

StoRM installation and Configuration

Line: 334 to 348
 

YAIM Configuration

Changed:
<
<
Before configure pay attention: if you are installing a new StoRM in a new host go on, if you are updating StoRM to new release follow this documentationuseful for the service and for the stored file patition:
* Upgrade_Instructions_to_StoRM_v18.pdf: Upgrade StoRM istructions. Useful to the data stored partition
>
>
Before configuring please pay attention:
  • if you are installing a new StoRM in a new host you can continue
  • if you are updating StoRM to a new release please follow this documentation containing useful information for the service upgrade and for the stored data files:
    * Upgrade_Instructions_to_StoRM_v18.pdf: Upgrade StoRM istructions.
 
Changed:
<
<
Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.
>
>
Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one.
 
Changed:
<
<
/opt/glite/yaim/bin/yaim -c -d 6 -s -n  se_storm_backend -n se_storm_frontend 2>&1 | tee /root/conf_StroRM_BE_FE.`hostname -s`.`date`.log
>
>
# /opt/glite/yaim/bin/yaim -c -d 6 -s -n  se_storm_backend -n se_storm_frontend 2>&1 | tee /root/conf_StroRM_BE_FE.`hostname -s`.`date`.log
  IMPORTANT NOTE The order of the profile is important and must be : -n se_storm_backend -n se_storm_frontend
Line: 348 to 364
  After service installation to have a look if all were installed in a proper way, you could have a look to Service StoRM Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
Added:
>
>

Documentation References:

 -- SergioTraldi - 2011-11-10

Revision 142011-11-22 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 192 to 192
 After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
Changed:
<
<

!StoRM installation and Configuration

>
>

StoRM installation and Configuration

  Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:
Line: 334 to 334
 

YAIM Configuration

Changed:
<
<
Before configure pay attention: if you are installing a new StoRM in a new host go on, if you are updating StoRM to new release follow this documentation Storm Migration before proceeding.
>
>
Before configure pay attention: if you are installing a new StoRM in a new host go on, if you are updating StoRM to new release follow this documentationuseful for the service and for the stored file patition:
* Upgrade_Instructions_to_StoRM_v18.pdf: Upgrade StoRM istructions. Useful to the data stored partition

  Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.
Line: 347 to 349
 After service installation to have a look if all were installed in a proper way, you could have a look to Service StoRM Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.

-- SergioTraldi - 2011-11-10

Added:
>
>

META FILEATTACHMENT attachment="Upgrade_Instructions_to_StoRM_v18.pdf" attr="" comment="Upgrade StoRM istructions. Useful to the data stored partition" date="1321956018" name="Upgrade_Instructions_to_StoRM_v18.pdf" path="Upgrade_Instructions_to_StoRM_v18.pdf" size="55433" user="SergioTraldi" version="1"

Revision 132011-11-17 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 86 to 86
 
yum install emi-bdii-site 
Added:
>
>
  • It's strongly recommended to install this openldap2.4 server to avoid frequent bdii crashes:
yum install openldap2.4-servers

 

Service Configuration

To proper configure the BDII site profile you have to customize this file with you site parameter:

Line: 95 to 101
 If you would like to cutomize the BDII_site service you can modify the variables in the service-specific file in the services/ directory. You will find an example in:
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site
Added:
>
>
* Remember to add the following variables to your site-info.def yaim configuration file and re-run yaim if you installed the openldap2.4-servers as recommended.

SLAPD=/usr/sbin/slapd2.4

 

YAIM Verification

Certificate will not expire.
Line: 163 to 173
 Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
Added:
>
>

Know Issue and Workaround

Missing /etc/bdii/gip/glite-info-site-defaults.conf : https://ggus.eu/tech/ticket_show.php?ticket=72561

Workaround: Check if the file exists and it's contents. If it's missing do:

echo "SITE_NAME=" > /etc/bdii/gip/glite-info-site-defaults.conf

Check also the permission of the directory opt/glite/var/cache/gip if it is not ldap:ldap change it:

chown -R ldap:ldap /opt/glite/var/cache/gip 
 

Service Testing - Reference Card

After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.

Revision 122011-11-16 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 180 to 180
 

Host certificate installation:

Changed:
<
<
Hosts participating to the StoRM-SE (FE, BE and GridFTP hosts) must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:
>
>
Hosts participating to the StoRM-SE (FE, BE and GridFTP hosts) must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:
  Check existence

Line: 200 to 200
 

ACL SUPPORT

Changed:
<
<
If you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue.
>
>
If you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue.
 StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly.

Check ACL:

Revision 112011-11-16 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 282 to 282
 

Service installation

Changed:
<
<
  • Install the StoRM metapackages, containing all packages needed by these four services:
>
>
  • Install the StoRM metapackages, containing all packages needed by these four services. You can install StoRM in one host or in more hosts. The mandatory profiles to install are emi-storm-backend-mp and emi-storm-frontend-mp. The other profiles are optional, have a look to the StoRM documentation System Administrator Guide to determinate if you need also emi-storm-globus-gridftp-mp or emi-storm-gridhttps-mp.
 
yum install emi-storm-backend-mp
yum install emi-storm-frontend-mp
yum install emi-storm-globus-gridftp-mp

Line: 310 to 310
 

YAIM Configuration

Added:
>
>
Before configure pay attention: if you are installing a new StoRM in a new host go on, if you are updating StoRM to new release follow this documentation Storm Migration before proceeding.
 Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.

/opt/glite/yaim/bin/yaim -c -d 6 -s -n  se_storm_backend -n se_storm_frontend 2>&1 | tee /root/conf_StroRM_BE_FE.`hostname -s`.`date`.log

Revision 102011-11-16 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 167 to 168
 After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
Changed:
<
<

StoRM installation and Configuration

>
>

!StoRM installation and Configuration

 
Changed:
<
<
Have a look to the section Repository Settings of this documentation, ensure to have the common repo files.
>
>
Have a look to the section Repository Settings and ensure that you have the common repo files.
 Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all
Changed:
<
<

StoRM Prerequisites

>
>

StoRM Prerequisites

 

Host certificate installation:

Changed:
<
<
Hosts participating to the StoRM-SE (FE, BE and GridFTP hosts) must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:
>
>
Hosts participating to the StoRM-SE (FE, BE and GridFTP hosts) must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:
  Check existence

Line: 200 to 201
 

ACL SUPPORT

If you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue.
Changed:
<
<
StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly.
>
>
StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly.
  Check ACL:

Line: 242 to 243
 This is valid for different file system types (i.e., ext3, xfs, gpfs and others).

EXTENDED ATTRIBUTE SUPPORT
Changed:
<
<
StoRM uses the Extended Attributes (EA) on files to store some metadata related to the file (e.g. the checksum value); therefore in order to ensure a proper running, the EA support needs to be enabled on the underlying file system and work properly.
>
>
StoRM uses the Extended Attributes (EA) on files to store some metadata related to the file (e.g. the checksum value); therefore in order to ensure a proper running, the EA support needs to be enabled on the underlying file system and work properly.
 Note: Depending on OS kernel distribution, for Reiser3, ext2 and ext3 file systems, the default kernel configuration should not enable the EA. Check Extended Attribute Support :
 

Line: 273 to 274
 
Changed:
<
<

CAa installation:

>
>

CAs installation:

 
Changed:
<
<
  • Install CAs on ALL profiles:
>
>
  • Install CAs on ALL profiles:
 
yum install ca-policy-egi-core

Service installation

Changed:
<
<
  • Install the StoRM metapackages, containing all packages needed by these four services:
>
>
  • Install the StoRM metapackages, containing all packages needed by these four services:
 
yum install emi-storm-backend-mp
yum install emi-storm-frontend-mp
yum install emi-storm-globus-gridftp-mp

Line: 290 to 291
 

Service Configuration

Changed:
<
<
To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter:
>
>
To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter:
  - ig-site-info.def
- ig-users.conf

Revision 92011-11-15 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 100 to 100
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site 
Changed:
<
<
The mandatory variabiles are:
>
>
The mandatory variables are:
  SITE_DESC
SITE_EMAIL
SITE_NAME
SITE_LOC
SITE_LAT
SITE_LONG
SITE_WEB
SITE_SECURITY_EMAIL
SITE_SUPPORT_EMAIL
SITE_OTHER_GRID
SITE_BDII_HOST
BDII_REGIONS
Changed:
<
<
Most of those are in the file ig-bdii_site in directory services (the better things is to modify it). Remeber in particular to set:
>
>
Most of those are in the file ig-bdii_site in directory services (the better things is to modify it). Remember in particular to set:
 
SITE_OTHER_GRID="WLCG|EGI"
SITE_OTHER_EGI_NGI="NGI_IT"
Line: 151 to 151
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_top 
Changed:
<
<
The mandatory variabile is:
>
>
The mandatory variable is:
  BDII_HOST
Line: 175 to 175
 
yum clean all
Changed:
<
<

Host certificate installation:

>
>

StoRM Prerequisites

Host certificate installation:

  Hosts participating to the StoRM-SE (FE, BE and GridFTP hosts) must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:

Check existence


Changed:
<
<
[~]# ls -l /etc/grid-security/hostkey.pem
-r-------- 1 root root 887 Mar 1 17:08 /etc/grid-security/hostkey.pem
[~]# ls -l /etc/grid-security/hostcert.pem
-rw-r--r-- 1 root root 1440 Mar 1 17:08 /etc/grid-security/hostcert.pem
>
>
[~]# ls -l /etc/grid-security/hostkey.pem -r-------- 1 root root 887 Mar 1 17:08 /etc/grid-security/hostkey.pem [~]# ls -l /etc/grid-security/hostcert.pem -rw-r--r-- 1 root root 1440 Mar 1 17:08 /etc/grid-security/hostcert.pem
 

Check expiration

Line: 192 to 194
  Change permission: (if needed)

Changed:
<
<
[~]# chmod 0400 hostkey.pem
[~]# chmod 0644 hostcert.pem
>
>
[~]# chmod 0400 hostkey.pem [~]# chmod 0644 hostcert.pem

ACL SUPPORT

If you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue. StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly.

Check ACL:

[~]# touch test
[~]# setfacl -m u:storm:rw test
Note: the storm user used to set the ACL entry must exist.
[~]# getfacl test
  # file: test
  # owner: root
  # group: root
  user::rw-
  user:storm:rw-
  group::r--
  mask::rw-
  other::r--

[~]# rm -f test

Install ACL (eventually):
If the getfacl and setfacl commands are not available on your host:

[~]# yum install acl

Enable ACL (if needed):
To enable ACL, you must add the acl property to the relevant file system in your /etc/fstab file. For example:

[~]# vi /etc/fstab
  ...
  /dev/hda3             /storage         ext3         defaults, acl           1 2
  ...

 
Added:
>
>
Then you need to remount the affected partitions as follows:
 [~]# mount -o remount /storage
This is valid for different file system types (i.e., ext3, xfs, gpfs and others).

EXTENDED ATTRIBUTE SUPPORT
StoRM uses the Extended Attributes (EA) on files to store some metadata related to the file (e.g. the checksum value); therefore in order to ensure a proper running, the EA support needs to be enabled on the underlying file system and work properly. Note: Depending on OS kernel distribution, for Reiser3, ext2 and ext3 file systems, the default kernel configuration should not enable the EA. Check Extended Attribute Support :
 
[~]# touch testfile
[~]# setfattr -n user.testea -v test testfile
[~]# getfattr -d testfile
  # file: testfile
  user.testea="test"
[~]# rm -f testfile

Install attr (eventually):
If the getfattr and setfattrl commands are not available on your host:

[~]# yum install attr

Enable EA (if needed):
To set extended attributes, you must add the user_xattr property to the relevant file systems in your /etc/fstab file. For example:

[~]# vi /etc/fstab
   ...
   /dev/hda3         /storage       ext3        defaults,acl,user_xattr     1 2
   ...

Then you need to remount the affected partitions as follows:

[~]# mount -o remount /storage
 

CAa installation:

  • Install CAs on ALL profiles:
Line: 204 to 281
 

Service installation

Changed:
<
<
  • Install the BDII_top metapackage, containing all packages needed by this service:
yum install emi-bdii-top 

>
>
  • Install the StoRM metapackages, containing all packages needed by these four services:
yum install emi-storm-backend-mp
yum install emi-storm-frontend-mp
yum install emi-storm-globus-gridftp-mp
yum install emi-storm-gridhttps-mp

 

Service Configuration

Changed:
<
<
To proper configure the BDII top profile you have to customize this file with you site parameter:
>
>
To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter:
 
Changed:
<
<
- ig-site-info.def
>
>
- ig-site-info.def
- ig-users.conf
- ig-groups.conf
 

YAIM Verification

Changed:
<
<
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_top 
>
>
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the StoRM profiles.
 
Changed:
<
<
The mandatory variabile is:
>
>
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  se_storm_backend -n se_storm_frontend
 
 
Changed:
<
<
BDII_HOST
>
>
You can find in this documentation: System Administrator Guide all mandatory variables. In the section GENERAL YAIM VARIABLES
 
Changed:
<
<
If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration.
>
>
If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration.
 

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.

Changed:
<
<
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
>
>
/opt/glite/yaim/bin/yaim -c -d 6 -s -n  se_storm_backend -n se_storm_frontend 2>&1 | tee /root/conf_StroRM_BE_FE.`hostname -s`.`date`.log

IMPORTANT NOTE The order of the profile is important and must be : -n se_storm_backend -n se_storm_frontend

 

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
>
>
After service installation to have a look if all were installed in a proper way, you could have a look to Service StoRM Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
 -- SergioTraldi - 2011-11-10

Revision 82011-11-15 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 38 to 38
 You need to have enabled only the above repositories (Operating System, EPEL, Certification Authority, EMI):
Common repositories *x86_64*
epel.repo
Changed:
<
<
emi.repo
>
>
emi.repo (emi1-base.repo emi1-third-party.repo emi1-updates.repo)
 
egi-trustanchors.repo
Changed:
<
<
To install emi repo files with its gp key associated install this rpm: rpm -ivh http://emisoft.web.cern.ch/emisoft/dist/EMI/1/sl5/x86_64/base/emi-release-1.0.0-1.sl5.noarch.rpm
>
>
To install emi repo files with its gp key associated install these packages to protect the base repo files and the rpm:
yum install yum-priorities yum-protectbase
rpm -ivh http://emisoft.web.cern.ch/emisoft/dist/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
 

Generic Configuration

Configuration files

Line: 66 to 67
 The optional folders are created to allow system administrators to organise their configurations in a more structured way.”

BDII Site installation and Configuration

Added:
>
>
Have a look to the section Repository Settings of this documentation, ensure to have the common repo files.
 Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all

Line: 93 to 95
 
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site

YAIM Verification

Added:
>
>
Certificate will not expire.
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site 
Line: 119 to 122
 

BDII Top installation and Configuration

Added:
>
>
Have a look to the section Repository Settings of this documentation, ensure to have the common repo files.
 Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all

Line: 162 to 166
  After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
Added:
>
>

StoRM installation and Configuration

Have a look to the section Repository Settings of this documentation, ensure to have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all

Host certificate installation:

Hosts participating to the StoRM-SE (FE, BE and GridFTP hosts) must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively:

Check existence

[~]# ls -l /etc/grid-security/hostkey.pem
-r-------- 1 root root 887 Mar 1 17:08 /etc/grid-security/hostkey.pem
[~]# ls -l /etc/grid-security/hostcert.pem
-rw-r--r-- 1 root root 1440 Mar 1 17:08 /etc/grid-security/hostcert.pem

Check expiration

[~]# openssl x509 -in hostcert.pem -noout -dates

Change permission: (if needed)

[~]# chmod 0400 hostkey.pem
[~]# chmod 0644 hostcert.pem

CAa installation:

  • Install CAs on ALL profiles:
yum install ca-policy-egi-core

Service installation

  • Install the BDII_top metapackage, containing all packages needed by this service:
yum install emi-bdii-top 

Service Configuration

To proper configure the BDII top profile you have to customize this file with you site parameter:

- ig-site-info.def

YAIM Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_top 

The mandatory variabile is:

BDII_HOST

If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration.

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.

/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log

Service Testing - Reference Card

After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.

 -- SergioTraldi - 2011-11-10

Revision 72011-11-14 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 38 to 38
 You need to have enabled only the above repositories (Operating System, EPEL, Certification Authority, EMI):
Common repositories *x86_64*
epel.repo
Changed:
<
<
emi.repo
>
>
emi.repo
 
egi-trustanchors.repo
Added:
>
>
To install emi repo files with its gp key associated install this rpm: rpm -ivh http://emisoft.web.cern.ch/emisoft/dist/EMI/1/sl5/x86_64/base/emi-release-1.0.0-1.sl5.noarch.rpm
 

Generic Configuration

Configuration files

IGI YAIM configuration files

Line: 82 to 85
 

Service Configuration

Changed:
<
<
To proper configure the BDII site profile you need this file:
>
>
To proper configure the BDII site profile you have to customize this file with you site parameter:
  - ig-site-info.def
Changed:
<
<
If you would like to cutomize the BDII_site service you can modify the varibles in the service-specific file in the services/ directory. You will find an example in:
>
>
If you would like to cutomize the BDII_site service you can modify the variables in the service-specific file in the services/ directory. You will find an example in:
 
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site

YAIM Verification

Line: 114 to 117
  After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_site Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.
Added:
>
>

BDII Top installation and Configuration

Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all

CAa installation:

  • Install CAs on ALL profiles:
yum install ca-policy-egi-core

Service installation

  • Install the BDII_top metapackage, containing all packages needed by this service:
yum install emi-bdii-top 

Service Configuration

To proper configure the BDII top profile you have to customize this file with you site parameter:

- ig-site-info.def

YAIM Verification

  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_top 

The mandatory variabile is:

BDII_HOST

If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration.

YAIM Configuration

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.

/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log

Service Testing - Reference Card

After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.

 -- SergioTraldi - 2011-11-10

Revision 62011-11-14 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 6 to 6
 

Installation

OS installation

Changed:
<
<
Install SL5 using SL5.X repository (CERN mirror) or one of the supported OS (RHEL5 clones).
>
>
Install SL5 using SL5.X repository (CERN mirror) or one of the supported OS (RHEL5 clones).
 
Changed:
<
<
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
>
>
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!
Line: 110 to 110
 Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
Changed:
<
<

Service Testing - Reference Card

>
>

Service Testing - Reference Card

  After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_site Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.

Revision 52011-11-14 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 43 to 43
 

Generic Configuration

Configuration files

Changed:
<
<
IGI YAIM configuration files
>
>

IGI 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 Example Details
Line: 68 to 68
 
yum clean all
Changed:
<
<

CAa installation:

>
>

CAa installation:

 
  • Install CAs on ALL profiles:
yum install ca-policy-egi-core
Changed:
<
<

Service installation

>
>

Service installation

 
  • Install the BDII_site metapackage, containing all packages needed by this service:
yum install emi-bdii-site 
Changed:
<
<

Service Configuration

>
>

Service Configuration

  To proper configure the BDII site profile you need this file:
Line: 89 to 89
 If you would like to cutomize the BDII_site service you can modify the varibles in the service-specific file in the services/ directory. You will find an example in:
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site
Changed:
<
<
YAIM Verification
>
>

YAIM Verification

 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site 
Line: 105 to 105
  If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration.
Changed:
<
<
YAIM Configuration
>
>

YAIM Configuration

  Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
Added:
>
>

Service Testing - Reference Card

After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_site Reference Card. In this page you can found were all the log files are written, what daemons are running after installation and any other useful service information.

 -- SergioTraldi - 2011-11-10

Revision 42011-11-11 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 70 to 70
 

CAa installation:

Changed:
<
<
Install CAs on ALL profiles:
>
>
  • Install CAs on ALL profiles:
 
yum install ca-policy-egi-core

Service installation

Changed:
<
<
Install all packages use for BDII site software
>
>
  • Install the BDII_site metapackage, containing all packages needed by this service:
 
yum install emi-bdii-site 
Line: 86 to 86
  - ig-site-info.def
Changed:
<
<
If you would like to cutomize the BDII_site service you can modify the varibles in the yaim services file. You should found an example in:
>
>
If you would like to cutomize the BDII_site service you can modify the varibles in the service-specific file in the services/ directory. You will find an example in:
 
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site

YAIM Verification
Changed:
<
<
Test if the site-info.def file is well set and you have all the mandatory variables set.
>
>
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables and that all configuration files contain all the site-specific values needed:
 
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site 

The mandatory variabiles are:

Line: 103 to 103
 SITE_OTHER_EGI_NGI="NGI_IT"
Changed:
<
<
If no errors occurred in the test you can proceed to the configuration.
>
>
If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration.
 
YAIM Configuration
Changed:
<
<
Please use this string to configure the services to have the maximum debug and to save all the configuration information in a log file you can look at any time.
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +DONEm%d-HELPM%S`.log
>
>
Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log
  -- SergioTraldi - 2011-11-10

Revision 32011-11-10 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 39 to 39
 
Common repositories *x86_64*
epel.repo
emi.repo
Changed:
<
<
egi-trustanchors.repo
>
>
egi-trustanchors.repo
 
Changed:
<
<

BDII Site installation and Configuration

>
>

Generic Configuration

Configuration files

IGI 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 Example Details
<your-site-info.def> whole-site ig-site-info.def 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 ig-users.conf 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: ”<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 ig-groups.conf 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.”

BDII Site installation and Configuration

  Before starting the installation procedure remember to clean all yum cache and headers:
Line: 64 to 84
  To proper configure the BDII site profile you need this file:
Changed:
<
<
- site-info.def
>
>
- ig-site-info.def
  If you would like to cutomize the BDII_site service you can modify the varibles in the yaim services file. You should found an example in:
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site
Changed:
<
<
Yaim Verification
>
>
YAIM Verification
  Test if the site-info.def file is well set and you have all the mandatory variables set.
 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site 
Line: 78 to 98
  SITE_DESC
SITE_EMAIL
SITE_NAME
SITE_LOC
SITE_LAT
SITE_LONG
SITE_WEB
SITE_SECURITY_EMAIL
SITE_SUPPORT_EMAIL
SITE_OTHER_GRID
SITE_BDII_HOST
BDII_REGIONS
Added:
>
>
Most of those are in the file ig-bdii_site in directory services (the better things is to modify it). Remeber in particular to set:
SITE_OTHER_GRID="WLCG|EGI"
SITE_OTHER_EGI_NGI="NGI_IT"
 If no errors occurred in the test you can proceed to the configuration.
Changed:
<
<
Yaim Configuration
>
>
YAIM Configuration
  Please use this string to configure the services to have the maximum debug and to save all the configuration information in a log file you can look at any time.
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +DONEm%d-HELPM%S`.log 
>
>
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +DONEm%d-HELPM%S`.log
  -- SergioTraldi - 2011-11-10

Revision 22011-11-10 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Deleted:
<
<

 

Installation

OS installation

Line: 19 to 18
 
 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).

Deleted:
<
<

 

Repository Settings

To have more details to the repository have a look to the this link Repository Specifications

Line: 68 to 65
 To proper configure the BDII site profile you need this file:

- site-info.def

Deleted:
<
<
- user.conf - group.conf
 
Changed:
<
<
/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n BDII_site
>
>
If you would like to cutomize the BDII_site service you can modify the varibles in the yaim services file. You should found an example in:
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site

Yaim Verification

Test if the site-info.def file is well set and you have all the mandatory variables set.

 /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site 

The mandatory variabiles are:

SITE_DESC
SITE_EMAIL
SITE_NAME
SITE_LOC
SITE_LAT
SITE_LONG
SITE_WEB
SITE_SECURITY_EMAIL
SITE_SUPPORT_EMAIL
SITE_OTHER_GRID
SITE_BDII_HOST
BDII_REGIONS

If no errors occurred in the test you can proceed to the configuration.

Yaim Configuration

Please use this string to configure the services to have the maximum debug and to save all the configuration information in a log file you can look at any time.

 /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +DONEm%d-HELPM%S`.log 
  -- SergioTraldi - 2011-11-10

Revision 12011-11-10 - SergioTraldi

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) 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

If not present by default on your SL5/x86_64 nodes, you should enable the EPEL repository (https://fedoraproject.org/wiki/EPEL)

EPEL has an 'epel-release' package that includes gpg keys for package signing and repository information. Installing this package, http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm, should allow you to use normal tools such as yum to install packages and their dependencies. By default the stable EPEL repo is enabled. Example of epel.repo file:

[extras]
name=epel
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch
protect=0

IMPORTANT NOTE

If present remember to disable the dag.repo if it is enabled.

You need to have enabled only the above repositories (Operating System, EPEL, Certification Authority, EMI):

Common repositories *x86_64*
epel.repo
emi.repo
egi-trustanchors.repo

BDII Site installation and Configuration

Before starting the installation procedure remember to clean all yum cache and headers:

yum clean all

CAa installation:

Install CAs on ALL profiles:

yum install ca-policy-egi-core

Service installation

Install all packages use for BDII site software

yum install emi-bdii-site 

Service Configuration

To proper configure the BDII site profile you need this file:

- site-info.def - user.conf - group.conf

/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n BDII_site

-- SergioTraldi - 2011-11-10

 
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