Difference: IgiEmi (1 vs. 2)

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