Difference: IgiEmi (14 vs. 15)

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
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback