Difference: IgiEmi (58 vs. 59)

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