Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 780 to 780 | ||||||||
/opt/glite/yaim/bin/yaim -c -d 6 -s | ||||||||
Added: | ||||||||
> > |
Known Issues
| |||||||
Service Testing - Reference CardAfter service installation you could have a look at WN - Service Reference Card. In this page you can find information on what daemons are running, log files, cron jobs, etc. |
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 109 to 109 | |||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
|
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 109 to 109 | |||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
Known issues
|
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 109 to 109 | |||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 1113 to 1113 | ||||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
HLR Documentation References: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 962 to 962 | ||||||||
Changed: | ||||||||
< < | HLR Server Installation and Configuration NEW | |||||||
> > | HLR Server Installation and Configuration NEW Update | |||||||
Extended Release Notes: | ||||||||
Added: | ||||||||
> > | ||||||||
HLR Prerequisites |
Line: 1 to 1 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||||
Line: 67 to 67 | ||||||||||
| ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
|
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 111 to 111 | |||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
Known issues
|
Line: 1 to 1 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||||
Line: 50 to 50 | ||||||||||
EPEL has an epel-release package that includes the gpg key used for package signing and other repository information, like the .repo files. Tto use normal tools such as yum to install packages and their dependencies | ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
By default the stable EPEL repo is enabled. Example of epel-5.repo file:
[extras] | ||||||||||
Line: 67 to 67 | ||||||||||
| ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 1038 to 1038 | ||||||||
| ||||||||
Added: | ||||||||
> > | Known Issue - IMPORTANT NOTEAfter configuration please change into the file /etc/cron.d/dgas the command from /usr/sbin/dgas-hlr-translatedb to /usr/sbin/dgas-hlr-populateJobTransSummary like the example below:cat /etc/cron.d/dgas # Cron file created by YAIM - don't modify it! SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root HOME=/ # Update hlr database */4 * * * * root /usr/sbin/dgas-hlr-populateJobTransSummary > /dev/null 2>&1This fix will be provide with the new yaim in next release. | |||||||
Post installation and configuration
| ||||||||
Line: 1080 to 1097 | ||||||||
# /usr/sbin/dgas-hlr-populateJobTransSummary
| ||||||||
Added: | ||||||||
> > |
| |||||||
Post Update Procedure |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 1046 to 1046 | ||||||||
Update From a previous release (< 4.0): | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 985 to 985 | ||||||||
Operating System | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Host certificate installation: | ||||||||
Line: 1009 to 1009 | ||||||||
Middleware Installation
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 1029 to 1029 | ||||||||
Verification
| ||||||||
Changed: | ||||||||
< < | # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n HLR | |||||||
> > | # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n HLR | |||||||
HLR Server Configuration | ||||||||
Line: 1046 to 1046 | ||||||||
Update From a previous release (< 4.0): | ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Line: 1056 to 1058 | ||||||||
| ||||||||
Changed: | ||||||||
< < | mysqldump --user=root --password hlr_Padova > /data/hlr.sql mysqldump --user=root --password hlr_tmp_Padova > /data/hlr_tmp.sql | |||||||
> > | mysqldump --user=root --password hlr > /data/hlr.sql mysqldump --user=root --password hlr_tmp > /data/hlr_tmp.sql | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 453 to 453 | ||||||||
# yum clean all | ||||||||
Changed: | ||||||||
< < | The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64.
| |||||||
> > | The CREAM CE Services were tested with gLite WN SL5/SL6 x86_64 and also with ig_WN SL5/SL6 x86_64. | |||||||
CREAM CE Prerequisites | ||||||||
Line: 663 to 662 | ||||||||
WN Installation and Configuration | ||||||||
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: | |||||||
> > |
| |||||||
Changed: | ||||||||
< < | # yum clean all | |||||||
> > |
| |||||||
WN Prerequisites | ||||||||
Line: 680 to 678 | ||||||||
CAs installation: | ||||||||
Changed: | ||||||||
< < |
# yum install ca-policy-egi-core | |||||||
> > |
| |||||||
Service installation | ||||||||
Changed: | ||||||||
< < |
# yum install <metapackage> emi-version;
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 711 to 713 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Service Configuration | ||||||||
Line: 728 to 730 | ||||||||
| ||||||||
Changed: | ||||||||
< < | For Torque:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_torque | |||||||
> > |
| |||||||
or | ||||||||
Changed: | ||||||||
< < | # /glite/yaim/bin/yaim -v -s <site-info.def> -n WN_torque_noafs | |||||||
> > | # /glite/yaim/bin/yaim -v -s <your-site-info.def> -n WN_torque_noafs | |||||||
Changed: | ||||||||
< < | For LSF:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_LSF | |||||||
> > |
| |||||||
or | ||||||||
Changed: | ||||||||
< < | # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_LSF_noafs | |||||||
> > | # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n WN_LSF_noafs | |||||||
Changed: | ||||||||
< < | For Other Batch System:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN | |||||||
> > |
| |||||||
Changed: | ||||||||
< < | You can find in this documentation: YAIM WN Variables all mandatory variables. | |||||||
> > | You can find all mandatory variables in this documentation: YAIM WN Variables | |||||||
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 with the configuration, otherwise correct them before continuing. | |||||||
YAIM Configuration
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Changed: | ||||||||
< < |
# /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > |
| |||||||
or | ||||||||
Changed: | ||||||||
< < | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <your-site-info.def> -n WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
| |||||||
Changed: | ||||||||
< < |
# /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > |
| |||||||
or | ||||||||
Changed: | ||||||||
< < | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <your-site-info.def> -n WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
| ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s | |||||||
Service Testing - Reference Card | ||||||||
Changed: | ||||||||
< < | After service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information. | |||||||
> > | After service installation you could have a look at WN - Service Reference Card. In this page you can find information on what daemons are running, log files, cron jobs, etc. | |||||||
WN Documentation References: | ||||||||
Added: | ||||||||
> > | ||||||||
Deleted: | ||||||||
< < | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
UI Installation and Configuration | ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
# yum clean all | |||||||
> > |
| |||||||
CAs installation: | ||||||||
Changed: | ||||||||
< < |
# yum install ca-policy-egi-core | |||||||
> > |
| |||||||
Service installation
| ||||||||
Changed: | ||||||||
< < |
# yum install emi-ui | |||||||
> > |
| |||||||
Service ConfigurationYAIM Verification | ||||||||
Changed: | ||||||||
< < |
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n UI | |||||||
> > |
| |||||||
Changed: | ||||||||
< < | You can find in this documentation: YAIM UI Variables all mandatory variables. | |||||||
> > | You can find all mandatory variables in this documentation: YAIM UI Variables | |||||||
Changed: | ||||||||
< < | If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing. | |||||||
> > | If no errors are reported during verification you can proceed with the configuration, otherwise correct them before continuing. | |||||||
YAIM Configuration
| ||||||||
Changed: | ||||||||
< < |
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > |
| |||||||
Service Testing - Reference Card | ||||||||
Changed: | ||||||||
< < | After service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can find some commonl errors and other useful service information. | |||||||
> > | After service installation you could have a look at the UI Reference Card or User Troubleshooting Guide. In this page you can find some common errors and other useful service information. | |||||||
UI Documentation References: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 1064 to 1064 | ||||||||
# mysql -u root -p hlr < /data/hlr.sql
| ||||||||
Changed: | ||||||||
< < | # nohup /usr/sbin/dgas-hlr-translatedb --D & | |||||||
> > | # nohup /usr/sbin/dgas-hlr-translatedb -D & | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 554 to 553 | ||||||||
# yum install emi-lsf-utils | ||||||||
Changed: | ||||||||
< < | DGAS_sensors installation UPDATEDIGI 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 | |||||||
> > | DGAS_sensors installation & upgradeExtended Release Notes: | |||||||
Added: | ||||||||
> > | IGI Release supports the use of DGAS as accounting system - please install also DGAS sensors on the CREAM node: | |||||||
# yum install igi-dgas_sensors | ||||||||
Added: | ||||||||
> > | Upgrade:
| |||||||
Middleware ConfigurationYAIM Verification | ||||||||
Line: 647 to 657 | ||||||||
* Service Troubleshooting Guide * Other Documentation available here | ||||||||
Added: | ||||||||
> > | DGAS Sensors Documentation References: | |||||||
WN Installation and ConfigurationHave a look to the section Repository Settings and ensure that you have the common repo files. | ||||||||
Line: 943 to 957 | ||||||||
HLR Server Installation and Configuration NEW | ||||||||
Added: | ||||||||
> > | Extended Release Notes: | |||||||
HLR Prerequisites |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 987 to 987 | ||||||||
Middleware Installation
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 554 to 554 | ||||||||
# yum install emi-lsf-utils | ||||||||
Changed: | ||||||||
< < | DGAS_sensors installation NEW | |||||||
> > | DGAS_sensors installation UPDATED | |||||||
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 | ||||||||
Line: 942 to 942 | ||||||||
Changed: | ||||||||
< < | HLR Server Installation and Configuration | |||||||
> > | HLR Server Installation and Configuration NEW | |||||||
HLR Prerequisites | ||||||||
Line: 988 to 988 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
# yum clean all | |||||||
> > |
| |||||||
CAs installation: | ||||||||
Changed: | ||||||||
< < |
# yum install ca-policy-egi-core | |||||||
> > |
| |||||||
HLR Server installation
| ||||||||
Changed: | ||||||||
< < |
# yum install igi-hlr | |||||||
> > |
| |||||||
Middleware ConfigurationVerification | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n HLR | ||||||||
Deleted: | ||||||||
< < | ||||||||
HLR Server Configuration | ||||||||
Line: 1021 to 1013 | ||||||||
HLR Server Configuration
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
# /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 Post installation and configuration | ||||||||
Changed: | ||||||||
< < | After the installation and configuration of the HLR Server services, you should register all the resources of the CEs attached to your HLR Server. Please use this command below for each CE:
# dgas-hlr-addadmin -Sa <CE_DN>Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it" | |||||||
> > |
| |||||||
Update From a previous release (< 4.0):
| ||||||||
Changed: | ||||||||
< < |
# /etc/init.d/glite-dgas-hlrd stop | |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
# df -hYou 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)
| |||||||
> > |
| |||||||
mysqldump --user=root --password hlr_Padova > /data/hlr.sql mysqldump --user=root --password hlr_tmp_Padova > /data/hlr_tmp.sql
| ||||||||
Changed: | ||||||||
< < | + Following the instructions in the previous section install the HLR Server and configure it using yaim.
# /etc/init.d/dgas-hlrd stop
| |||||||
> > |
| |||||||
# mysql -u root -p hlr_tmp < /data/hlr_tmp.sql # mysql -u root -p hlr < /data/hlr.sql | ||||||||
Changed: | ||||||||
< < |
]# nohup /usr/sbin/dgas-hlr-translatedb --D &
# /etc/init.d/dgas-hlrd start | |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
# /usr/sbin/dgas-hlr-populateJobTransSummary
# /etc/init.d/dgas-hlrd restart | |||||||
> > |
| |||||||
Post Update Procedure | ||||||||
Changed: | ||||||||
< < | After the update of the HLR Server Services, you should register again all the resources of the CE attached to your HLR Server. Please use this command below for each CE: | |||||||
> > | After the update of the HLR Server , you should register again all the resources of the CE attached to your HLR Server. Please use this command below for each CE: | |||||||
# dgas-hlr-addadmin -Sa <CE_DN> |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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.
| ||||||||
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. | |||||||
> > |
| |||||||
Once you have obtained a valid certificate: | ||||||||
Line: 508 to 505 | ||||||||
yum install ca-policy-egi-core | ||||||||
Changed: | ||||||||
< < | Service installation | |||||||
> > | Middleware installation | |||||||
| ||||||||
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 | ||||||||
| ||||||||
Changed: | ||||||||
< < | yum install emi-torque-server yum install emi-torque-utils | |||||||
> > | # yum install emi-torque-server # yum install emi-torque-utils | |||||||
| ||||||||
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 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
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. | |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | The suggested requirements are:
| |||||||
Co-Hosting | ||||||||
Changed: | ||||||||
< < | Due to the 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. | |||||||
> > |
| |||||||
Changed: | ||||||||
< < | Host certificate installation: | |||||||
> > | Operating System
| |||||||
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 | |||||||
> > |
| |||||||
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 | |||||||
> > |
| |||||||
[~]# openssl x509 -in hostcert.pem -noout -dates | ||||||||
Changed: | ||||||||
< < |
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: | |||||||
> > |
| |||||||
# yum clean all | ||||||||
Line: 1001 to 1002 | ||||||||
HLR Server installation | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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. | |||||||
> > |
| |||||||
HLR Server Configuration
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
# /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 : | |||||||
> > |
| |||||||
# /etc/init.d/glite-dgas-hlrd stop | ||||||||
Changed: | ||||||||
< < | Check disk space Ensure you have enough space in the disk: | |||||||
> > |
| |||||||
# df -hYou 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 : | |||||||
> > |
| |||||||
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: | |||||||
> > |
| |||||||
# /etc/init.d/dgas-hlrd stop | ||||||||
Changed: | ||||||||
< < | 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 | |||||||
> > |
| |||||||
]# nohup /usr/sbin/dgas-hlr-translatedb --D & | ||||||||
Changed: | ||||||||
< < | Start dgas services : | |||||||
> > |
| |||||||
# /etc/init.d/dgas-hlrd start | ||||||||
Changed: | ||||||||
< < | Execute populateJobTransSummary: The new HLR version need to polulate the JobTransSummary | |||||||
> > |
| |||||||
# /usr/sbin/dgas-hlr-populateJobTransSummary | ||||||||
Changed: | ||||||||
< < | Restart dgas services : | |||||||
> > |
| |||||||
# /etc/init.d/dgas-hlrd restart | ||||||||
Line: 1106 to 1094 | ||||||||
HLR Documentation References: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
|
Line: 1 to 1 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||||
Line: 67 to 67 | ||||||||||
| ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 36 to 36 | ||||||||
If you don't find useful information in this documentation please have also a look to the official EMI documentation: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Added: | ||||||||
> > | ||||||||
Repository Settings | ||||||||
Line: 48 to 49 | ||||||||
If not present by default on your SL6/x86_64 nodes, you should enable the EPEL repository (https://fedoraproject.org/wiki/EPEL)
EPEL has an epel-release package that includes the gpg key used for package signing and other repository information, like the .repo files. | ||||||||
Changed: | ||||||||
< < | For SL5/x86_64 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. For SL6/x86_64 installing this package, http://ftp-stud.hs-esslingen.de/pub/epel//6/x86_64/epel-release-6-7.noarch.rpm | |||||||
> > | Tto use normal tools such as yum to install packages and their dependencies
| |||||||
Changed: | ||||||||
< < | By default the stable EPEL repo is enabled. Example of epel.repo file: | |||||||
> > | By default the stable EPEL repo is enabled. Example of epel-5.repo file: | |||||||
[extras] name=epel mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch | ||||||||
Line: 61 to 63 | ||||||||
IMPORTANT NOTE:
| ||||||||
Changed: | ||||||||
< < | You need to have enabled only the following repositories (Operating System, EPEL, Certification Authority, EMI): | |||||||
> > | You need to have enabled only the following repositories: Operating System, EPEL, Certification Authority, EMI, IGI. Please see the table bellow for details: | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Changed: | ||||||||
< < | package containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL: | |||||||
> > | It is strongly recommended the use of the lastest version of the emi-release packages mentioned above as they containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL. Example:for EMI 1 case | |||||||
Added: | ||||||||
> > | # rpm --import http://emisoft.web.cern.ch/emisoft/dist/EMI/1/RPM-GPG-KEY-emi | |||||||
# wget http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm # yum localinstall emi-release-1.0.1-1.sl5.noarch.rpm |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 944 to 944 | ||||||||
HLR Server Installation and Configuration | ||||||||
Deleted: | ||||||||
< < | 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: # yum clean all | |||||||
HLR PrerequisitesHardware Requirements | ||||||||
Changed: | ||||||||
< < | The HLR server host should be an real or virtual host 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: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | Co-HostingDue to the critical nature the HLR server should be installed as a stand-alone service.Virtual vs. Physical | |||||||
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.
Host certificate installation: | ||||||||
Line: 985 to 980 | ||||||||
[~]# chmod 0600 hostcert.pem | ||||||||
Changed: | ||||||||
< < | CAs installation: | |||||||
> > | Middleware InstallationHave 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: # yum clean all CAs installation: | |||||||
# yum install ca-policy-egi-core | ||||||||
Changed: | ||||||||
< < | Service installation | |||||||
> > | HLR Server installation | |||||||
| ||||||||
Line: 999 to 1003 | ||||||||
# yum install igi-hlr; | ||||||||
Changed: | ||||||||
< < | Service Configuration | |||||||
> > | Middleware Configuration | |||||||
Changed: | ||||||||
< < | YAIM Verification | |||||||
> > | Verification | |||||||
| ||||||||
Line: 1009 to 1013 | ||||||||
If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing. | ||||||||
Changed: | ||||||||
< < | YAIM Configuration | |||||||
> > | HLR Server Configuration | |||||||
| ||||||||
Line: 1018 to 1022 | ||||||||
Post installation and configuration | ||||||||
Changed: | ||||||||
< < | After the installation and configuration of the HLR Server Services, you should register all the resources of the CE attached to your HLR Server. Please use this command below for each CE: | |||||||
> > | After the installation and configuration of the HLR Server services, you should register all the resources of the CEs attached to your HLR Server. Please use this command below for each CE: | |||||||
# dgas-hlr-addadmin -Sa <CE_DN> |
Line: 1 to 1 | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||||||||
Line: 45 to 45 | |||||||||||||||||||
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 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: | ||||||||||||||||||
> > | If not present by default on your SL6/x86_64 nodes, you should enable the EPEL repository (https://fedoraproject.org/wiki/EPEL)
EPEL has an epel-release package that includes the gpg key used for package signing and other repository information, like the .repo files. For SL5/x86_64 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. For SL6/x86_64 installing this package, http://ftp-stud.hs-esslingen.de/pub/epel//6/x86_64/epel-release-6-7.noarch.rpm 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 | |||||||||||||||||||
Line: 56 to 62 | |||||||||||||||||||
| |||||||||||||||||||
Changed: | |||||||||||||||||||
< < |
| ||||||||||||||||||
> > |
| ||||||||||||||||||
It is strongly recommended the use of the lastest version of the emi-release 1
package containing the EMI public key and the yum .repo files, that ensures the precedence of EMI repositories over EPEL:
| |||||||||||||||||||
Changed: | |||||||||||||||||||
< < | # 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 | ||||||||||||||||||
> > | # wget http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm # yum localinstall emi-release-1.0.1-1.sl5.noarch.rpm | ||||||||||||||||||
Deleted: | |||||||||||||||||||
< < | EMI 2 repos file:
| ||||||||||||||||||
Updating from EMI 1 to EMI 2For the update to EMI 2 you have to uninstall the old emi-release package and install the new one: | |||||||||||||||||||
Line: 562 to 558 | |||||||||||||||||||
If you use DGAS to account data remember to install also DGAS sensors. You can found more documentation to DGAS sensors guide
| |||||||||||||||||||
Changed: | |||||||||||||||||||
< < | yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers yaim-dgas | ||||||||||||||||||
> > | yum install igi-dgas_sensors | ||||||||||||||||||
Service Configuration | |||||||||||||||||||
Line: 945 to 941 | |||||||||||||||||||
Added: | |||||||||||||||||||
> > |
HLR Server Installation and ConfigurationHave 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: # yum clean all HLR PrerequisitesHardware RequirementsThe HLR server host should be an real or virtual host having an optimal disk access. The suggested requirements are:
Host certificate installation: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: 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.pemCheck expiration [~]# openssl x509 -in hostcert.pem -noout -datesChange permission: (if needed) [~]# chmod 0400 hostkey.pem [~]# chmod 0600 hostcert.pem CAs installation:
# yum install ca-policy-egi-core Service installation
# yum install igi-hlr; Service ConfigurationYAIM Verification
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n HLRIf no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing. YAIM Configuration
# /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 Post installation and configurationAfter the installation and configuration of the HLR Server Services, you should register all the resources of the CE attached to your HLR Server. Please use this command below for each CE:# dgas-hlr-addadmin -Sa <CE_DN>Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it" Update From previous release:Back up the old databases : Form previous HLR Server stop the dgas services and make a dump of the databases: Stop the services :# /etc/init.d/glite-dgas-hlrd stopCheck disk space Ensure you have enough space in the disk: # df -hYou 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) Make the dump : mysqldump --user=root --password hlr_Padova > /data/hlr.sql mysqldump --user=root --password hlr_tmp_Padova > /data/hlr_tmp.sqlInstallation : 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: # /etc/init.d/dgas-hlrd stopRestore the dump : # mysql -u root -p hlr_tmp < /data/hlr_tmp.sql # mysql -u root -p hlr < /data/hlr.sqlexecute translate DB ]# nohup /usr/sbin/dgas-hlr-translatedb --D &Start dgas services : # /etc/init.d/dgas-hlrd startExecute populateJobTransSummary: The new HLR version need to polulate the JobTransSummary # /usr/sbin/dgas-hlr-populateJobTransSummaryRestart dgas services : # /etc/init.d/dgas-hlrd restart Post Update ProcedureAfter the update of the HLR Server Services, you should register again all the resources of the CE attached to your HLR Server. Please use this command below for each CE:# dgas-hlr-addadmin -Sa <CE_DN>Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it" HLR Documentation References: | ||||||||||||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 679 to 679 | ||||||||
| ||||||||
Changed: | ||||||||
< < | # yum install <metapackage> | |||||||
> > | # yum install <metapackage> emi-version; | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 163 to 163 | ||||||||
# yum install emi-bdii-site | ||||||||
Deleted: | ||||||||
< < |
# yum install openldap2.4-servers | |||||||
Service ConfigurationTo proper configure the BDII site profile you have to customize this file with you site parameter: | ||||||||
Line: 178 to 172 | ||||||||
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 | ||||||||
Deleted: | ||||||||
< < |
| |||||||
YAIM Verification |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 284 to 284 | ||||||||
IMPORTANT NOTES: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 398 to 398 | ||||||||
Service installation | ||||||||
Deleted: | ||||||||
< < |
| |||||||
* 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, emi-storm-frontend-mp and emi-storm-globus-gridftp-mp. The other profiles are optional, have a look to the StoRM documentation System Administrator Guide to determinate if you need also emi-storm-gridhttps-mp or checksum. The most common installation using one host: | ||||||||
Line: 422 to 416 | ||||||||
YAIM Verification | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n se_storm_backend -n se_storm_frontend -n se_storm_gridftp |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 131 to 131 | ||||||||
NTP ConfigurationCheck if the NTP is installed in your O.S. | ||||||||
Changed: | ||||||||
< < | In the repo igi-emi.repo is present a rpm called yaim-addons. Please install it: | |||||||
> > | If you have installed the middleware, and you have the package glite-yaim-core in your host you have to get the repo igi-emi.repo and inside it there is a rpm called yaim-addons. Please install it: | |||||||
wget http://repo-pd.italiangrid.it/mrepo/repos/igi/sl5/x86_64/igi-emi.repo |
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 109 to 109 | |||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 283 to 283 | ||||||||
yum clean all | ||||||||
Added: | ||||||||
> > | IMPORTANT NOTES:
| |||||||
StoRM PrerequisitesHost certificate installation: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 101 to 101 | ||||||||
Tips & Tricks:
| ||||||||
Deleted: | ||||||||
< < | Globus 5.2 Issues and temporary workarounddue 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:
# /etc/init.d/dpm-gsiftp restart
# service storm-globus-gridftp restart | |||||||
Generic ConfigurationConfiguration filesIGI YAIM configuration files |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 32 to 32 | ||||||||
... and then reboot the system. | ||||||||
Added: | ||||||||
> > | EMI release useful linkIf you don't find useful information in this documentation please have also a look to the official EMI documentation: * EMI 1 product pages * EMI 1 update pages * EMI 2 product pages | |||||||
Repository SettingsTo have more details to the repository have a look to the this link Repository Specifications | ||||||||
Line: 56 to 63 | ||||||||
| ||||||||
Changed: | ||||||||
< < | 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: | |||||||
> > | It is strongly recommended the use of the lastest version of the emi-release 1 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 | ||||||||
Added: | ||||||||
> > | EMI 2 repos file:
Updating from EMI 1 to EMI 2For the update to EMI 2 you have to uninstall the old emi-release package and install the new one:# rpm -e emi-release # rpm -ivh http://emisoft.web.cern.ch/emisoft/dist/EMI/2/sl5/x86_64/base/emi-release-2.0.0-1.sl5.noarch.rpm | |||||||
Important note on automatic updatesSeveral site use auto update mechanism. Sometimes middleware updates require non-trivial configuration changes or a reconfiguration of the service. This could involve service restarts, new configuration files, etc, which makes it difficult to ensure that automatic updates will not break a service. Thus |
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 101 to 101 | |||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
|
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 98 to 98 | |||||||||||||
IGI YAIM configuration filesYAIM configuration files should be stored in a directory structure. All the involved files HAVE to be under the same folder <confdir>, in a safe place, which is not world readable. This directory should contain: | |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
Known issues
|
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 101 to 101 | |||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
Known issues
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 119 to 119 | ||||||||
The optional folders are created to allow system administrators to organise their configurations in a more structured way.” | ||||||||
Added: | ||||||||
> > | NTP ConfigurationCheck if the NTP is installed in your O.S.In the repo igi-emi.repo is present a rpm called yaim-addons. Please install it: wget http://repo-pd.italiangrid.it/mrepo/repos/igi/sl5/x86_64/igi-emi.repo yum install yaim-addonsAfter that you can use yaim to configure ntrp: /opt/glite/yaim/bin/yaim -r -d 6 -s <site-info.def> -n <node_type> -f config_ntp | |||||||
BDII Site installation and ConfigurationHave a look to the section Repository Settings of this documentation and ensure to have the common .repo files. | ||||||||
Line: 371 to 386 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | * 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, emi-storm-frontend-mp and emi-storm-globus-gridftp-mp. The other profiles are optional, have a look to the StoRM documentation System Administrator Guide to determinate if you need also emi-storm-gridhttps-mp or checksum. The most common installation using one host: | |||||||
yum install emi-storm-backend-mp yum install emi-storm-frontend-mp yum install emi-storm-globus-gridftp-mp | ||||||||
Deleted: | ||||||||
< < | yum install emi-storm-gridhttps-mp | |||||||
Service Configuration |
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||
Line: 833 to 833 | |||||||||||||
# yum install glite-mpi
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
| |||||||||||||
Line: 857 to 857 | |||||||||||||
| |||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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: | ||||||||
> > | Tips & Tricks:
| |||||||
Globus 5.2 Issues and temporary workarounddue 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. |
Line: 1 to 1 | |||||||||
---|---|---|---|---|---|---|---|---|---|
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 workarounddue 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:
# /etc/init.d/dpm-gsiftp restart
# service storm-globus-gridftp restart | ||||||||
Generic ConfigurationConfiguration filesIGI YAIM configuration files | |||||||||
Line: 81 to 101 | |||||||||
| |||||||||
Added: | |||||||||
> > | Known issues
| ||||||||
Additional filesFurthermore 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 | |||||||||
| |||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 338 to 338 | ||||||||
Service installation | ||||||||
Added: | ||||||||
> > |
| |||||||
yum install emi-storm-backend-mp yum install emi-storm-frontend-mp |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 716 to 716 | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
UI Installation and Configuration |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 62 to 62 | ||||||||
# rpm -ivh http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm | ||||||||
Added: | ||||||||
> > | Important note on automatic updatesSeveral site use auto update mechanism. Sometimes middleware updates require non-trivial configuration changes or a reconfiguration of the service. This could involve service restarts, new configuration files, etc, which makes it difficult to ensure that automatic updates will not break a service. Thus WE STRONGLY RECOMMEND NOT TO USE AUTOMATIC UPDATE PROCEDURE OF ANY KIND 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! | |||||||
Generic ConfigurationConfiguration filesIGI YAIM configuration files |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 597 to 597 | ||||||||
Before starting the installation procedure remember to clean all yum cache and headers:
| ||||||||
Changed: | ||||||||
< < | yum clean all | |||||||
> > | # yum clean all | |||||||
WN Prerequisites | ||||||||
Line: 611 to 611 | ||||||||
CAs installation:
| ||||||||
Changed: | ||||||||
< < | yum install ca-policy-egi-core | |||||||
> > | # yum install ca-policy-egi-core | |||||||
Service installation | ||||||||
Line: 619 to 619 | ||||||||
| ||||||||
Changed: | ||||||||
< < | yum install <metapackage> | |||||||
> > | # yum install <metapackage> | |||||||
| ||||||||
Line: 659 to 659 | ||||||||
| ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_torque | |||||||
> > | # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_torque | |||||||
or | ||||||||
Changed: | ||||||||
< < | /glite/yaim/bin/yaim -v -s <site-info.def> -n WN_torque_noafs | |||||||
> > | # /glite/yaim/bin/yaim -v -s <site-info.def> -n WN_torque_noafs | |||||||
For LSF: | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_LSF | |||||||
> > | # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_LSF | |||||||
or | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_LSF_noafs | |||||||
> > | # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_LSF_noafs | |||||||
For Other Batch System: | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN | |||||||
> > | # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN | |||||||
You can find in this documentation: YAIM WN Variables all mandatory variables. | ||||||||
Line: 687 to 687 | ||||||||
| ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
or | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
| ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
or | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | ||||||||
Line: 715 to 715 | ||||||||
| ||||||||
Changed: | ||||||||
< < | yum clean all | |||||||
> > | # yum clean all | |||||||
CAs installation:
| ||||||||
Changed: | ||||||||
< < | yum install ca-policy-egi-core | |||||||
> > | # yum install ca-policy-egi-core | |||||||
Service installation | ||||||||
Line: 729 to 729 | ||||||||
| ||||||||
Changed: | ||||||||
< < | yum install emi-ui | |||||||
> > | # yum install emi-ui | |||||||
Service Configuration | ||||||||
Line: 738 to 738 | ||||||||
| ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n UI | |||||||
> > | # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n UI | |||||||
You can find in this documentation: YAIM UI Variables all mandatory variables. | ||||||||
Line: 769 to 769 | ||||||||
| ||||||||
Changed: | ||||||||
< < | yum clean all | |||||||
> > | # yum clean all | |||||||
MPI Service installation on CE-CREAM | ||||||||
Changed: | ||||||||
< < | Follow the CE-CREAM installation guide before starting to follow this steps below | |||||||
> > |
| |||||||
Changed: | ||||||||
< < | yum install glite-mpi | |||||||
> > | # yum install glite-mpi | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
MPI Service installation on WN | ||||||||
Changed: | ||||||||
< < | Follow the WN installation guide before starting to follow this steps below | |||||||
> > |
| |||||||
Changed: | ||||||||
< < | yum install glite-mpi | |||||||
> > | # yum install glite-mpi
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Changed: | ||||||||
< < | If you would like to use the OPEN MPI flavour in your site please install:
yum install openmpi openmpi-develIf you would like to use the MPICH2 flavour in your site please install: yum install mpich2
Service Configuration | |||||||
> > | Service Configuration | |||||||
Useful Variables | ||||||||
Changed: | ||||||||
< < | Remember to copy these three files in your service directory:
| |||||||
> > |
| |||||||
| ||||||||
Line: 850 to 830 | ||||||||
YAIM Verification
| ||||||||
Changed: | ||||||||
< < |
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_WN -n WN_torque_noafsYou can find in this documentation: YAIM MPI Variables all mandatory variables. If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing. | |||||||
> > |
| |||||||
YAIM Configuration | ||||||||
Line: 869 to 843 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > | ||||||||
| ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 2>&1 | tee /root/conf_EMI_CREAM_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 2>&1 | tee /root/conf_EMI_CREAM_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
| ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_WN -n WN_torque_noafs 2>&1 | tee /root/conf_WN_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_WN -n WN_torque_noafs 2>&1 | tee /root/conf_WN_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
Check files in WN | ||||||||
Changed: | ||||||||
< < | If in YAIM Configuration you are chose to use MPI_SSH_HOST_BASED_AUTH (well-advised) check these files:
| |||||||
> > |
| |||||||
Changed: | ||||||||
< < | The first one sshd_config should have the follow variables set like below | |||||||
> > |
| |||||||
HostbasedAuthentication yes IgnoreUserKnownHosts yes IgnoreRhosts yes | ||||||||
Changed: | ||||||||
< < | The second file shosts.equiv should contains: the CE hostname, the default SE host name and all the WNs hostname. May be in the CE it was created in configuration process, copy it form the CE.
Restart sshd services after file modification:
service sshd restart | |||||||
> > |
° service sshd restart | |||||||
Service Testing - Reference Card | ||||||||
Changed: | ||||||||
< < | After service installation to have a look if all were installed in a proper way, you could have a look to Service Reference Card and User & Service Troubleshooting Guide. In this page you can find some common errors and other useful service information. | |||||||
> > |
| |||||||
MPI Documentation References: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 778 to 778 | ||||||||
Follow the CE-CREAM installation guide before starting to follow this steps below
| ||||||||
Changed: | ||||||||
< < | yum install mpi-start glite-yaim-mpi | |||||||
> > | yum install glite-mpi | |||||||
Added: | ||||||||
> > |
| |||||||
MPI Service installation on WNFollow the WN installation guide before starting to follow this steps below | ||||||||
Changed: | ||||||||
< < | yum install mpi-start glite-yaim-mpi yum install openmpi openmpi-devel mpich2 | |||||||
> > | yum install glite-mpi
yum install openmpi openmpi-develIf you would like to use the MPICH2 flavour in your site please install: yum install mpich2 | |||||||
| ||||||||
Line: 877 to 898 | ||||||||
Service Testing - Reference Card | ||||||||
Changed: | ||||||||
< < | After service installation to have a look if all were installed in a proper way, you could have a look to User & Service Troubleshooting Guide. In this page you can find some common errors and other useful service information. | |||||||
> > | After service installation to have a look if all were installed in a proper way, you could have a look to Service Reference Card and User & Service Troubleshooting Guide. In this page you can find some common errors and other useful service information. | |||||||
MPI Documentation References: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 137 to 137 | ||||||||
SITE_OTHER_EGI_NGI="NGI_IT" | ||||||||
Changed: | ||||||||
< < | If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration. | |||||||
> > | If no errors are reported you can proceed to the configuration, otherwise correct them before continuing. | |||||||
YAIM Configuration | ||||||||
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 you can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one. | |||||||
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log Service Testing - Reference Card |
Line: 1 to 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Line: 708 to 708 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
UI Installation and Configuration | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Line: 764 to 764 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
MPI Installation and Configuration
yum clean all MPI Service installation on CE-CREAMFollow the CE-CREAM installation guide before starting to follow this steps belowyum install mpi-start glite-yaim-mpi MPI Service installation on WNFollow the WN installation guide before starting to follow this steps belowyum install mpi-start glite-yaim-mpi yum install openmpi openmpi-devel mpich2
Service ConfigurationUseful VariablesRemember to copy these three files in your service directory:
YAIM Verification
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n MPI_WN -n WN_torque_noafsYou can find in this documentation: YAIM MPI Variables all mandatory variables. If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing. YAIM Configuration
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_CE -n creamCE -n TORQUE_server -n TORQUE_utils 2>&1 | tee /root/conf_EMI_CREAM_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n MPI_WN -n WN_torque_noafs 2>&1 | tee /root/conf_WN_Torque_MPI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log Check files in WNIf in YAIM Configuration you are chose to use MPI_SSH_HOST_BASED_AUTH (well-advised) check these files:
HostbasedAuthentication yes IgnoreUserKnownHosts yes IgnoreRhosts yesThe second file shosts.equiv should contains: the CE hostname, the default SE host name and all the WNs hostname. May be in the CE it was created in configuration process, copy it form the CE. Restart sshd services after file modification: service sshd restart Service Testing - Reference CardAfter service installation to have a look if all were installed in a proper way, you could have a look to User & Service Troubleshooting Guide. In this page you can find some common errors and other useful service information.MPI Documentation References: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 591 to 591 | ||||||||
Changed: | ||||||||
< < | WN Installation and Configuration - WORK IN PROGRESS | |||||||
> > | WN 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: | ||||||||
Line: 616 to 616 | ||||||||
Service installation | ||||||||
Changed: | ||||||||
< < | Install the WN metapackages, containing all packages needed. Have a look to the WN documentation before starting to install: WN Guides. IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of theese: | |||||||
> > |
yum install <metapackage>
| |||||||
| ||||||||
Changed: | ||||||||
< < | Note: the igi-wn metapackage is useful for SGE or other Batch System
yum install <metapackage> | |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | IMPORTANT NOTE FOR TORQUE:
After the Torque installation you should have the version 2.5.7-7. Please remember to copy the munge key from the batch master to the WN just installed
scp <batch master host>:/etc/munge/munge.key /etc/munge | |||||||
Added: | ||||||||
> > |
| |||||||
Service Configuration | ||||||||
Line: 664 to 673 | ||||||||
You can find in this documentation: YAIM WN Variables all mandatory variables. | ||||||||
Changed: | ||||||||
< < | If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration. | |||||||
> > | If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing. | |||||||
YAIM Configuration | ||||||||
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 default one. | |||||||
> > |
| |||||||
| ||||||||
Line: 676 to 686 | ||||||||
| ||||||||
Changed: | ||||||||
< < | For Torque: | |||||||
> > |
| |||||||
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.logor /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | ||||||||
Changed: | ||||||||
< < | For LSF: | |||||||
> > |
| |||||||
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.logor /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | ||||||||
Changed: | ||||||||
< < | For Other Batch System: | |||||||
> > |
| |||||||
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log Service Testing - Reference Card | ||||||||
Changed: | ||||||||
< < | After service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information. | |||||||
> > | After service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information. | |||||||
WN Documentation References: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
| ||||||||
Added: | ||||||||
> > | UI Installation and Configuration | |||||||
Changed: | ||||||||
< < |
UI Installation and Configuration - WORK IN PROGRESSHave 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: | |||||||
> > |
| |||||||
yum clean all | ||||||||
Line: 718 to 725 | ||||||||
Service installation | ||||||||
Changed: | ||||||||
< < | Install the UI metapackages, containing all packages needed. Have a look to the UI documentation before starting to install: UI Guides. | |||||||
> > |
| |||||||
yum install emi-ui | ||||||||
Line: 729 to 736 | ||||||||
YAIM Verification | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n UIYou can find in this documentation: YAIM UI Variables all mandatory variables. | ||||||||
Changed: | ||||||||
< < | If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration. | |||||||
> > | If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing. | |||||||
YAIM Configuration | ||||||||
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 default one. | |||||||
> > |
| |||||||
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log Service Testing - Reference Card | ||||||||
Changed: | ||||||||
< < | After service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can found some typical problems occured and any other useful service information. | |||||||
> > | After service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can find some commonl errors and other useful service information. | |||||||
UI Documentation References: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 142 to 142 | ||||||||
YAIM ConfigurationPlease 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. | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
Service Testing - Reference Card | ||||||||
Line: 192 to 192 | ||||||||
YAIM ConfigurationPlease 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. | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
Know Issue and Workaround | ||||||||
Line: 366 to 366 | ||||||||
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 -n se_storm_gridftp 2>&1 | tee /root/conf_StroRM_BE_FE_Gftp.`hostname -s`.`date`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s -n se_storm_backend -n se_storm_frontend -n se_storm_gridftp 2>&1 | tee /root/conf_StroRM_BE_FE_Gftp.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
IMPORTANT NOTE The order of the profile is important and must be : -n se_storm_backend -n se_storm_frontend | ||||||||
Line: 564 to 564 | ||||||||
For Torque: | ||||||||
Changed: | ||||||||
< < | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_Torque_DGAS.`hostname -s`.`date`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_Torque_DGAS.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
For LSF: | ||||||||
Changed: | ||||||||
< < | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n creamCE -n LSF_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_LSF_DGAS.`hostname -s`.`date`.log | |||||||
> > | # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n creamCE -n LSF_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_LSF_DGAS.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
Service Testing - Reference Card | ||||||||
Line: 677 to 677 | ||||||||
For Torque: | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
or | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
For LSF: | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
or | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
For Other Batch System: | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
Service Testing - Reference Card | ||||||||
Line: 742 to 742 | ||||||||
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 <site-info.def> -n UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log | |||||||
Service Testing - Reference Card |
Line: 1 to 1 | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||||||||||||||||||||
Line: 76 to 76 | ||||||||||||||||||||||||||
Additional filesFurthermore the configuration folder can contain: | ||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||
The optional folders are created to allow system administrators to organise their configurations in a more structured way.” | ||||||||||||||||||||||||||
Line: 176 to 176 | ||||||||||||||||||||||||||
To proper configure the BDII top profile you have to customize this file with you site parameter: | ||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||
< < | - ig-site-info.def | |||||||||||||||||||||||||
> > | ||||||||||||||||||||||||||
YAIM Verification | ||||||||||||||||||||||||||
Line: 341 to 341 | ||||||||||||||||||||||||||
To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter: | ||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||
< < | - ig-site-info.def - ig-users.conf - ig-groups.conf | |||||||||||||||||||||||||
> > | ||||||||||||||||||||||||||
YAIM Verification | ||||||||||||||||||||||||||
Line: 402 to 402 | ||||||||||||||||||||||||||
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: 466 to 467 | ||||||||||||||||||||||||||
yum install emi-torque-utils | ||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||
< < | * If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage: | |||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||
yum install emi-torque-utils | ||||||||||||||||||||||||||
Line: 549 to 550 | ||||||||||||||||||||||||||
USE_ARGUS=no | ||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||
< < | DGAS_sensors: | |||||||||||||||||||||||||
> > | DGAS_sensors: | |||||||||||||||||||||||||
For DGAS_sensors you should customize the services file. You can find in this path an example:
/opt/glite/yaim/examples/siteinfo/services/dgas_sensors | ||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||
YAIM ConfigurationPlease 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. | ||||||||||||||||||||||||||
Line: 618 to 618 | ||||||||||||||||||||||||||
Install the WN metapackages, containing all packages needed. Have a look to the WN documentation before starting to install: WN Guides. IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of theese: | ||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||
yum install <metapackage> | ||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||
< < | IMPORTANT NOTE: All the metapackages name are case sensitive, you have to write it as described above. | |||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||
IMPORTANT NOTE FOR TORQUE: After the Torque installation you should have the version 2.5.7-7. Please remember to copy the munge key from the batch master to the WN just installed | ||||||||||||||||||||||||||
Line: 665 to 670 | ||||||||||||||||||||||||||
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: | ||||||||||||||||||||||||||
< < | IMPORTANT NOTE: All the profiles name are case sensitive, you have to write it as described above. | |||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||
For Torque:
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date`.log |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 591 to 591 | ||||||||
Added: | ||||||||
> > | WN Installation and Configuration - WORK IN PROGRESSHave 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: yum clean all WN PrerequisitesBatch System:
CAs installation:
yum install ca-policy-egi-core Service installationInstall the WN metapackages, containing all packages needed. Have a look to the WN documentation before starting to install: WN Guides. IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of theese:
yum install <metapackage>IMPORTANT NOTE: All the metapackages name are case sensitive, you have to write it as described above. IMPORTANT NOTE FOR TORQUE: After the Torque installation you should have the version 2.5.7-7. Please remember to copy the munge key from the batch master to the WN just installed scp <batch master host>:/etc/munge/munge.key /etc/munge Service ConfigurationYAIM Verification
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_torqueor /glite/yaim/bin/yaim -v -s <site-info.def> -n WN_torque_noafsFor LSF: /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_LSFor /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WN_LSF_noafsFor Other Batch System: /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n WNYou can find in this documentation: YAIM WN Variables all mandatory variables. If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration. YAIM ConfigurationPlease 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.
IMPORTANT NOTE: All the profiles name are case sensitive, you have to write it as described above. For Torque: /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date`.logor /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date`.logFor LSF: /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date`.logor /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date`.logFor Other Batch System: /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date`.log Service Testing - Reference CardAfter service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information.WN Documentation References:
UI Installation and Configuration - WORK IN PROGRESSHave 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: yum clean all CAs installation:
yum install ca-policy-egi-core Service installationInstall the UI metapackages, containing all packages needed. Have a look to the UI documentation before starting to install: UI Guides.yum install emi-ui Service ConfigurationYAIM Verification
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n UIYou can find in this documentation: YAIM UI Variables all mandatory variables. If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration. YAIM ConfigurationPlease 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.
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date`.log Service Testing - Reference CardAfter service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can found some typical problems occured and any other useful service information.UI Documentation References: | |||||||
|
Line: 1 to 1 | |||||||||
---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | |||||||||
Line: 68 to 68 | |||||||||
YAIM configuration files should be stored in a directory structure. All the involved files HAVE to be under the same folder <confdir>, in a safe place, which is not world readable. This directory should contain:
| |||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
| |||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
Additional files |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 571 to 571 | ||||||||
Service Testing - Reference Card | ||||||||
Changed: | ||||||||
< < | After service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card and also to the [http://wiki.italiangrid.it/twiki/bin/view/CREAM/CreamTestWorkPlan][Service Troubleshooting Guide]]. 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. | |||||||
> > | After service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card and also to the Service Troubleshooting Guide. 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. | |||||||
CREAM Documentation References: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 349 to 349 | ||||||||
| ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n se_storm_backend -n se_storm_frontend | |||||||
> > | /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n se_storm_backend -n se_storm_frontend -n se_storm_gridftp | |||||||
You can find in this documentation: System Administrator Guide all mandatory variables. In the section GENERAL YAIM VARIABLES | ||||||||
Line: 366 to 366 | ||||||||
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 -n se_storm_gridftp 2>&1 | tee /root/conf_StroRM_BE_FE_Gftp.`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: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 244 to 244 | ||||||||
Change permission: (if needed) [~]# chmod 0400 hostkey.pem | ||||||||
Changed: | ||||||||
< < | [~]# chmod 0644 hostcert.pem | |||||||
> > | [~]# chmod 0600 hostcert.pem | |||||||
ACL SUPPORT | ||||||||
Line: 425 to 425 | ||||||||
Change permission: (if needed) [~]# chmod 0400 hostkey.pem | ||||||||
Changed: | ||||||||
< < | [~]# chmod 0644 hostcert.pem | |||||||
> > | [~]# chmod 0600 hostcert.pem | |||||||
Batch System: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 472 to 472 | ||||||||
yum install emi-torque-utils | ||||||||
Added: | ||||||||
> > | 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.
rpm -qa | grep munge munge-libs-0.5.8-8.el5 munge-0.5.8-8.el5To enable munge on your torque cluster:
| |||||||
* If you are running LSF, install the emi-lsf-utils metapackage:
yum install emi-lsf-utils |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 538 to 538 | ||||||||
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. | ||||||||
Added: | ||||||||
> > | IMPORTANT NOTE: For Torque was found an error in starting pbs_server so if you are configuring the PBS server NODE before launching yaim remember to start pbs_server: /etc/init.d/pbs_server start | |||||||
For Torque:
# /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_Torque_DGAS.`hostname -s`.`date`.log |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 54 to 54 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
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:
| ||||||||
Line: 481 to 482 | ||||||||
If you use DGAS to account data remember to install also DGAS sensors. You can found more documentation to DGAS sensors guide
| ||||||||
Changed: | ||||||||
< < | yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers
Install also yaim-dgas rpm this could be useful when you will configure DGAS_sensors
rpm -ivh http://repo-pd.italiangrid.it/mrepo/ig_sl5-x86_64/RPMS.3_2_0/yaim-dgas-5.0.0-3.noarch.rpm | |||||||
> > | yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers yaim-dgas | |||||||
Service Configuration |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 386 to 386 | ||||||||
Changed: | ||||||||
< < | CREAM CE installation and Configuration | |||||||
> > | CREAM CE 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: | ||||||||
Line: 394 to 394 | ||||||||
yum clean all | ||||||||
Changed: | ||||||||
< < | The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64. We remember the Toque Server and client work only if the CE and the WN is SL5 x86_64 and the MAUI version is equal in the server and client side. Please update the WN if you have an old installation. | |||||||
> > | The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64.
| |||||||
CREAM CE PrerequisitesHost certificate installation: | ||||||||
Changed: | ||||||||
< < | In the host were CREAM CE is intalled 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: | |||||||
> > | 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:
| |||||||
Check existence | ||||||||
Line: 421 to 429 | ||||||||
Batch System: | ||||||||
Changed: | ||||||||
< < | If you will use LSF (licences are needed). The server/client installation must be done manually. Have a look to Platform LSF documentation, whereas Torque server/client installation is included in the Toque metapackages. | |||||||
> > |
Access to batch system log filesIt doesn't matter what kind of deployment you have, batch-system master on a different machine than the CE (TORQUE or LSF) or on the same one, you have to be sure that you provide access to the batch system log files: You must set up a mechanism to transfer accounting logs to the CE:
| |||||||
CAs installation: | ||||||||
Line: 438 to 454 | ||||||||
yum install emi-cream-ce | ||||||||
Changed: | ||||||||
< < | Batch system utility installation | |||||||
> > | Batch System Utilities installation | |||||||
After the installation of the CREAM CE metapackage it is necessary to install the batch system specific metapackage(s): | ||||||||
Line: 536 to 552 | ||||||||
After service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card and also to the [http://wiki.italiangrid.it/twiki/bin/view/CREAM/CreamTestWorkPlan][Service Troubleshooting Guide]]. 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. | ||||||||
Changed: | ||||||||
< < | Documentation References: | |||||||
> > | CREAM Documentation References: | |||||||
* Functional Description * Software Design Description | ||||||||
Line: 554 to 570 | ||||||||
Deleted: | ||||||||
< < | -- SergioTraldi - 2011-11-10 | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration
| ||||||||
Changed: | ||||||||
< < | Installation | |||||||
> > | Common Installation | |||||||
OS installation |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 386 to 386 | ||||||||
Added: | ||||||||
> > | CREAM CE installation and ConfigurationHave 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: yum clean allThe CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64. We remember the Toque Server and client work only if the CE and the WN is SL5 x86_64 and the MAUI version is equal in the server and client side. Please update the WN if you have an old installation. CREAM CE PrerequisitesHost certificate installation:In the host were CREAM CE is intalled 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.pemCheck expiration [~]# openssl x509 -in hostcert.pem -noout -datesChange permission: (if needed) [~]# chmod 0400 hostkey.pem [~]# chmod 0644 hostcert.pem Batch System:If you will use LSF (licences are needed). The server/client installation must be done manually. Have a look to Platform LSF documentation, whereas Torque server/client installation is included in the Toque metapackages.CAs installation:
yum install ca-policy-egi-core Service 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.yum install xml-commons-apis yum install emi-cream-ce Batch system utility installationAfter the installation of the CREAM CE metapackage it is necessary to install the batch system specific metapackage(s): * If you are running Torque, and your CREAM CE node is the torque master, install the emi-torque-server and emi-torque-utils metapackages: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: yum install emi-torque-utils* If you are running LSF, install the emi-lsf-utils metapackage: yum install emi-lsf-utils DGAS_sensors installationIf you use DGAS to account data remember to install also DGAS sensors. You can found more documentation to DGAS sensors guideyum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producersInstall also yaim-dgas rpm this could be useful when you will configure DGAS_sensors rpm -ivh http://repo-pd.italiangrid.it/mrepo/ig_sl5-x86_64/RPMS.3_2_0/yaim-dgas-5.0.0-3.noarch.rpm Service ConfigurationYAIM Verification
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensorsFor LSF: /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n creamCE -n LSF_utils -n DGAS_sensorsYou can find in this documentation: YAIM CREAM CE Variables all mandatory variables. If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration. Configuration Suggestions:Blparser:We suggest to use the new Blparser runs on the CREAM CE machine and it is automatically installed when installing the CREAM CE. The configuration of the new BLAH Blparser is done when configuring the CREAM CE (i.e. it is not necessary to configure the Blparser separately from the CREAM CE). To use the new BLAH blparser, it is just necessary to set: BLPARSER_WITH_UPDATER_NOTIFIER=trueARGUS: If you have an ARGUS server installed in your site or in central site we suggest to use it. Please set the proper variables: USE_ARGUS=yesIn this case it is also necessary to set the following yaim variables: * ARGUS_PEPD_ENDPOINTS The endpoint of the ARGUS box (e.g."https://cream-43.pd.infn.it:8154/authz") * CREAM_PEPC_RESOURCEID The id of the CREAM CE in the ARGUS box (e.g. "http://pd.infn.it/cream-18") If instead gJAF should be used as authorization system, yaim variable USE_ARGUS must be set in the following way: USE_ARGUS=noDGAS_sensors: For DGAS_sensors you should customize the services file. You can find in this path an example: /opt/glite/yaim/examples/siteinfo/services/dgas_sensors YAIM ConfigurationPlease 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.
For Torque:
# /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_Torque_DGAS.`hostname -s`.`date`.logFor LSF: # /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n creamCE -n LSF_utils -n DGAS_sensors 2>&1 | tee /root/conf_CREAM_LSF_DGAS.`hostname -s`.`date`.log Service Testing - Reference CardAfter service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card and also to the [http://wiki.italiangrid.it/twiki/bin/view/CREAM/CreamTestWorkPlan][Service Troubleshooting Guide]]. 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.Documentation References:* Functional Description* Software Design Description * User Guide * Client Installation and Configuration * Client Configuration Template * Man Pages/Online Help * User Troubleshooting Guide * API Documentation * Error Code Documentation * System Administrator Guides * Service Reference Card * Service Troubleshooting Guide * Other Documentation available here | |||||||
-- SergioTraldi - 2011-11-10 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 22 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 ). | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | Disabling SELinuxPlease remember to fully disabling SELinux. Disabling will completely disable all SELinux functions including file and process labelling. In RedHat Enterprise, edit /etc/selinux/config and change the SELINUX line to SELINUX=disabled:# disabled - No SELinux policy is loaded. SELINUX=disabled... and then reboot the system. | |||||||
Repository SettingsTo have more details to the repository have a look to the this link Repository Specifications |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 182 to 182 | ||||||||
YAIM ConfigurationPlease 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. | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log | |||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_top 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log | |||||||
Know Issue and Workaround |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 SettingsTo 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:
| |||||||
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): | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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 ConfigurationConfiguration files | ||||||||
Line: 66 to 73 | ||||||||
| ||||||||
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: | |||||||
yum install ca-policy-egi-core | ||||||||
Line: 83 to 91 | ||||||||
Service installation
| ||||||||
Changed: | ||||||||
< < | yum install emi-bdii-site | |||||||
> > | # yum install emi-bdii-site | |||||||
| ||||||||
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. | |||||||
/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 ConfigurationHave 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:
| |||||||
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 192 to 192 | ||||||||
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. | ||||||||
Changed: | ||||||||
< < | !StoRM installation and Configuration | |||||||
> > | StoRM 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: | ||||||||
Line: 334 to 334 | ||||||||
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 documentation Storm Migration before proceeding. | |||||||
> > | 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 | |||||||
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. | ||||||||
Line: 347 to 349 | ||||||||
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. -- SergioTraldi - 2011-11-10 | ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 86 to 86 | ||||||||
yum install emi-bdii-site | ||||||||
Added: | ||||||||
> > |
yum install openldap2.4-servers | |||||||
Service ConfigurationTo proper configure the BDII site profile you have to customize this file with you site parameter: | ||||||||
Line: 95 to 101 | ||||||||
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 | ||||||||
Added: | ||||||||
> > | * Remember to add the following variables to your site-info.def yaim configuration file and re-run yaim if you installed the openldap2.4-servers as recommended. SLAPD=/usr/sbin/slapd2.4 | |||||||
YAIM VerificationCertificate will not expire. | ||||||||
Line: 163 to 173 | ||||||||
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 | ||||||||
Added: | ||||||||
> > | Know Issue and WorkaroundMissing /etc/bdii/gip/glite-info-site-defaults.conf : https://ggus.eu/tech/ticket_show.php?ticket=72561 Workaround: Check if the file exists and it's contents. If it's missing do:echo "SITE_NAME=Check also the permission of the directory opt/glite/var/cache/gip if it is not ldap:ldap change it: chown -R ldap:ldap /opt/glite/var/cache/gip | |||||||
Service Testing - Reference CardAfter 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. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 180 to 180 | ||||||||
Host certificate installation: | ||||||||
Changed: | ||||||||
< < | 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: | |||||||
> > | 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 | ||||||||
Line: 200 to 200 | ||||||||
ACL SUPPORT | ||||||||
Changed: | ||||||||
< < | If you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue. | |||||||
> > | If you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue. | |||||||
StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly. Check ACL: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 282 to 282 | ||||||||
Service installation | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
yum install emi-storm-backend-mp yum install emi-storm-frontend-mp yum install emi-storm-globus-gridftp-mp | ||||||||
Line: 310 to 310 | ||||||||
YAIM Configuration | ||||||||
Added: | ||||||||
> > | 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 documentation Storm Migration before proceeding. | |||||||
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 se_storm_backend -n se_storm_frontend 2>&1 | tee /root/conf_StroRM_BE_FE.`hostname -s`.`date`.log |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 167 to 168 | ||||||||
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. | ||||||||
Changed: | ||||||||
< < | StoRM installation and Configuration | |||||||
> > | !StoRM 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 and ensure that you have the common repo files. | |||||||
Before starting the installation procedure remember to clean all yum cache and headers:
yum clean all | ||||||||
Changed: | ||||||||
< < | StoRM Prerequisites | |||||||
> > | StoRM Prerequisites | |||||||
Host certificate installation: | ||||||||
Changed: | ||||||||
< < | 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: | |||||||
> > | 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 | ||||||||
Line: 200 to 201 | ||||||||
ACL SUPPORTIf you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue. | ||||||||
Changed: | ||||||||
< < | StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly. | |||||||
> > | StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly. | |||||||
Check ACL:
| ||||||||
Line: 242 to 243 | ||||||||
This is valid for different file system types (i.e., ext3, xfs, gpfs and others).
EXTENDED ATTRIBUTE SUPPORT | ||||||||
Changed: | ||||||||
< < | StoRM uses the Extended Attributes (EA) on files to store some metadata related to the file (e.g. the checksum value); therefore in order to ensure a proper running, the EA support needs to be enabled on the underlying file system and work properly. | |||||||
> > | StoRM uses the Extended Attributes (EA) on files to store some metadata related to the file (e.g. the checksum value); therefore in order to ensure a proper running, the EA support needs to be enabled on the underlying file system and work properly. | |||||||
Note: Depending on OS kernel distribution, for Reiser3, ext2 and ext3 file systems, the default kernel configuration should not enable the EA.
Check Extended Attribute Support :
| ||||||||
Line: 273 to 274 | ||||||||
Changed: | ||||||||
< < | CAa installation: | |||||||
> > | CAs installation: | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
yum install ca-policy-egi-core Service installation | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
yum install emi-storm-backend-mp yum install emi-storm-frontend-mp yum install emi-storm-globus-gridftp-mp | ||||||||
Line: 290 to 291 | ||||||||
Service Configuration | ||||||||
Changed: | ||||||||
< < | To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter: | |||||||
> > | To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter: | |||||||
- ig-site-info.def - ig-users.conf |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 100 to 100 | ||||||||
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site | ||||||||
Changed: | ||||||||
< < | The mandatory variabiles are: | |||||||
> > | The mandatory variables 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 | ||||||||
Changed: | ||||||||
< < | Most of those are in the file ig-bdii_site in directory services (the better things is to modify it). Remeber in particular to set: | |||||||
> > | Most of those are in the file ig-bdii_site in directory services (the better things is to modify it). Remember in particular to set: | |||||||
SITE_OTHER_GRID="WLCG|EGI" SITE_OTHER_EGI_NGI="NGI_IT" | ||||||||
Line: 151 to 151 | ||||||||
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_top | ||||||||
Changed: | ||||||||
< < | The mandatory variabile is: | |||||||
> > | The mandatory variable is: | |||||||
BDII_HOST | ||||||||
Line: 175 to 175 | ||||||||
yum clean all | ||||||||
Changed: | ||||||||
< < | Host certificate installation: | |||||||
> > | StoRM PrerequisitesHost 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 | ||||||||
Changed: | ||||||||
< < | [~]# 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 | |||||||
> > | [~]# 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 | ||||||||
Line: 192 to 194 | ||||||||
Change permission: (if needed) | ||||||||
Changed: | ||||||||
< < | [~]# chmod 0400 hostkey.pem [~]# chmod 0644 hostcert.pem | |||||||
> > | [~]# chmod 0400 hostkey.pem
[~]# chmod 0644 hostcert.pem
ACL SUPPORTIf you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue. StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly. Check ACL:[~]# touch test [~]# setfacl -m u:storm:rw testNote: the storm user used to set the ACL entry must exist. [~]# getfacl test # file: test # owner: root # group: root user::rw- user:storm:rw- group::r-- mask::rw- other::r-- [~]# rm -f testInstall ACL (eventually): If the getfacl and setfacl commands are not available on your host: [~]# yum install aclEnable ACL (if needed): To enable ACL, you must add the acl property to the relevant file system in your /etc/fstab file. For example: [~]# vi /etc/fstab ... /dev/hda3 /storage ext3 defaults, acl 1 2 ... | |||||||
Added: | ||||||||
> > | Then you need to remount the affected partitions as follows:
[~]# mount -o remount /storageThis is valid for different file system types (i.e., ext3, xfs, gpfs and others). EXTENDED ATTRIBUTE SUPPORTStoRM uses the Extended Attributes (EA) on files to store some metadata related to the file (e.g. the checksum value); therefore in order to ensure a proper running, the EA support needs to be enabled on the underlying file system and work properly. Note: Depending on OS kernel distribution, for Reiser3, ext2 and ext3 file systems, the default kernel configuration should not enable the EA. Check Extended Attribute Support :[~]# touch testfile [~]# setfattr -n user.testea -v test testfile [~]# getfattr -d testfile # file: testfile user.testea="test" [~]# rm -f testfileInstall attr (eventually): If the getfattr and setfattrl commands are not available on your host: [~]# yum install attrEnable EA (if needed): To set extended attributes, you must add the user_xattr property to the relevant file systems in your /etc/fstab file. For example: [~]# vi /etc/fstab ... /dev/hda3 /storage ext3 defaults,acl,user_xattr 1 2 ...Then you need to remount the affected partitions as follows: [~]# mount -o remount /storage | |||||||
CAa installation:
| ||||||||
Line: 204 to 281 | ||||||||
Service installation | ||||||||
Changed: | ||||||||
< < |
yum install emi-bdii-top | |||||||
> > |
yum install emi-storm-backend-mp yum install emi-storm-frontend-mp yum install emi-storm-globus-gridftp-mp yum install emi-storm-gridhttps-mp | |||||||
Service Configuration | ||||||||
Changed: | ||||||||
< < | To proper configure the BDII top profile you have to customize this file with you site parameter: | |||||||
> > | To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter: | |||||||
Changed: | ||||||||
< < | - ig-site-info.def | |||||||
> > | - ig-site-info.def - ig-users.conf - ig-groups.conf | |||||||
YAIM Verification | ||||||||
Changed: | ||||||||
< < |
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_top | |||||||
> > |
| |||||||
Changed: | ||||||||
< < | The mandatory variabile is: | |||||||
> > | /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n se_storm_backend -n se_storm_frontend | |||||||
Changed: | ||||||||
< < | BDII_HOST | |||||||
> > | You can find in this documentation: System Administrator Guide all mandatory variables. In the section GENERAL YAIM VARIABLES | |||||||
Changed: | ||||||||
< < | If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration. | |||||||
> > | If no errors are reported with the verification you can proceed to the configuration, otherwise correct them before continuing with the configuration. | |||||||
YAIM ConfigurationPlease 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. | ||||||||
Changed: | ||||||||
< < | /opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_top 2>&1 | tee /root/conf_BDII.`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`.logIMPORTANT NOTE The order of the profile is important and must be : -n se_storm_backend -n se_storm_frontend | |||||||
Service Testing - Reference Card | ||||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | 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. | |||||||
-- SergioTraldi - 2011-11-10 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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):
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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 ConfigurationConfiguration 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. | |||||||
/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 ConfigurationHave 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.pemCheck expiration [~]# openssl x509 -in hostcert.pem -noout -datesChange permission: (if needed) [~]# chmod 0400 hostkey.pem CAa installation:
yum install ca-policy-egi-core Service installation
yum install emi-bdii-top Service ConfigurationTo proper configure the BDII top profile you have to customize this file with you site parameter: - ig-site-info.defYAIM Verification
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_topThe 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 ConfigurationPlease 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 CardAfter 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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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):
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > | 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 | |||||||
Generic ConfigurationConfiguration filesIGI YAIM configuration files | ||||||||
Line: 82 to 85 | ||||||||
Service Configuration | ||||||||
Changed: | ||||||||
< < | To proper configure the BDII site profile you need this file: | |||||||
> > | To proper configure the BDII site profile you have to customize this file with you site parameter: | |||||||
- ig-site-info.def | ||||||||
Changed: | ||||||||
< < | If you would like to cutomize the BDII_site service you can modify the varibles in the service-specific file in the services/ directory. You will find an example in: | |||||||
> > | 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 YAIM Verification | ||||||||
Line: 114 to 117 | ||||||||
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: | ||||||||
> > | BDII Top installation and ConfigurationBefore starting the installation procedure remember to clean all yum cache and headers:yum clean all CAa installation:
yum install ca-policy-egi-core Service installation
yum install emi-bdii-top Service ConfigurationTo proper configure the BDII top profile you have to customize this file with you site parameter: - ig-site-info.defYAIM Verification
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_topThe 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 ConfigurationPlease 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 CardAfter 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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 6 to 6 | ||||||||
InstallationOS installation | ||||||||
Changed: | ||||||||
< < | Install SL5 using SL5.X repository (CERN mirror) or one of the supported OS (RHEL5 clones). | |||||||
> > | 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 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: 110 to 110 | ||||||||
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_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log | ||||||||
Changed: | ||||||||
< < | Service Testing - Reference Card | |||||||
> > | 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_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. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 43 to 43 | ||||||||
Generic ConfigurationConfiguration files | ||||||||
Changed: | ||||||||
< < | IGI YAIM configuration files | |||||||
> > | IGI YAIM configuration files | |||||||
YAIM configuration files should be stored in a directory structure. All the involved files HAVE to be under the same folder <confdir>, in a safe place, which is not world readable. This directory should contain:
| ||||||||
Line: 68 to 68 | ||||||||
yum clean all | ||||||||
Changed: | ||||||||
< < | CAa installation: | |||||||
> > | CAa installation: | |||||||
yum install ca-policy-egi-core | ||||||||
Changed: | ||||||||
< < | Service installation | |||||||
> > | Service installation | |||||||
yum install emi-bdii-site | ||||||||
Changed: | ||||||||
< < | Service Configuration | |||||||
> > | Service Configuration | |||||||
To proper configure the BDII site profile you need this file: | ||||||||
Line: 89 to 89 | ||||||||
If you would like to cutomize the BDII_site service you can modify the varibles in the service-specific file in the services/ directory. You will find an example in:
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site | ||||||||
Changed: | ||||||||
< < | YAIM Verification | |||||||
> > | YAIM Verification | |||||||
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_site | ||||||||
Line: 105 to 105 | ||||||||
If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration. | ||||||||
Changed: | ||||||||
< < | YAIM 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_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log | ||||||||
Added: | ||||||||
> > | Service Testing - Reference CardAfter 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. | |||||||
-- SergioTraldi - 2011-11-10 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 70 to 70 | ||||||||
CAa installation: | ||||||||
Changed: | ||||||||
< < | Install CAs on ALL profiles: | |||||||
> > |
| |||||||
yum install ca-policy-egi-core Service installation | ||||||||
Changed: | ||||||||
< < | Install all packages use for BDII site software | |||||||
> > |
| |||||||
yum install emi-bdii-site | ||||||||
Line: 86 to 86 | ||||||||
- ig-site-info.def | ||||||||
Changed: | ||||||||
< < | 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: | |||||||
> > | If you would like to cutomize the BDII_site service you can modify the varibles in the service-specific file in the services/ directory. You will find an example in: | |||||||
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site YAIM Verification | ||||||||
Changed: | ||||||||
< < | 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_siteThe mandatory variabiles are: | ||||||||
Line: 103 to 103 | ||||||||
SITE_OTHER_EGI_NGI="NGI_IT" | ||||||||
Changed: | ||||||||
< < | If no errors occurred in the test you can proceed to the configuration. | |||||||
> > | If no errors are reported you can proceed to the configuration, otherwise correct them before continuing with the configuration. | |||||||
YAIM Configuration | ||||||||
Changed: | ||||||||
< < | 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 -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +m%d-M%S`.log | |||||||
> > | 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_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date`.log | |||||||
-- SergioTraldi - 2011-11-10 |
Line: 1 to 1 | ||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||||||||||||||||||||||||||||||||||||||||
Line: 39 to 39 | ||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < | BDII Site installation and Configuration | |||||||||||||||||||||||||||||||||||||||||||||
> > | Generic ConfigurationConfiguration filesIGI YAIM configuration filesYAIM configuration files should be stored in a directory structure. All the involved files HAVE to be under the same folder <confdir>, in a safe place, which is not world readable. This directory should contain:
Additional filesFurthermore the configuration folder can contain:
BDII Site installation and Configuration | |||||||||||||||||||||||||||||||||||||||||||||
Before starting the installation procedure remember to clean all yum cache and headers: | ||||||||||||||||||||||||||||||||||||||||||||||
Line: 64 to 84 | ||||||||||||||||||||||||||||||||||||||||||||||
To proper configure the BDII site profile you need this file: | ||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < | - site-info.def | |||||||||||||||||||||||||||||||||||||||||||||
> > | - ig-site-info.def | |||||||||||||||||||||||||||||||||||||||||||||
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 | ||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < | Yaim Verification | |||||||||||||||||||||||||||||||||||||||||||||
> > | 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 | ||||||||||||||||||||||||||||||||||||||||||||||
Line: 78 to 98 | ||||||||||||||||||||||||||||||||||||||||||||||
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 | ||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||
> > | Most of those are in the file ig-bdii_site in directory services (the better things is to modify it). Remeber in particular to set:
SITE_OTHER_GRID="WLCG|EGI" SITE_OTHER_EGI_NGI="NGI_IT" | |||||||||||||||||||||||||||||||||||||||||||||
If no errors occurred in the test you can proceed to the configuration. | ||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < | Yaim 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. | ||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < |
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +m%d-M%S`.log | |||||||||||||||||||||||||||||||||||||||||||||
> > | /opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +m%d-M%S`.log | |||||||||||||||||||||||||||||||||||||||||||||
-- SergioTraldi - 2011-11-10 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration
| ||||||||
Deleted: | ||||||||
< < | ||||||||
InstallationOS installation | ||||||||
Line: 19 to 18 | ||||||||
hostname -fIt 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 SettingsTo 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 VerificationTest 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_siteThe 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 ConfigurationPlease 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 +m%d-M%S`.log | |||||||
-- SergioTraldi - 2011-11-10 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
IGI (based on EMI) Installation and Configuration
InstallationOS installationInstall 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 YUMIf 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 hostnameEnsure that the hostnames of your machines are correctly set. Run the command:hostname -fIt 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 SettingsTo 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=0IMPORTANT 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):
BDII Site installation and ConfigurationBefore 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 installationInstall all packages use for BDII site softwareyum install emi-bdii-site Service ConfigurationTo 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 |