Difference: IgiEmi (7 vs. 8)

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