Difference: IgiEmi (38 vs. 39)

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

StoRM-GridFTP-Server

 # 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.

View topic | History: r77 < r76 < r75 < r74 | More topic actions...