OPS/FAQs/Install_glite_Apel

0. It is assumed that you have a SL5 x86_84 installed

1. Install mysql-server and add a password for root user

2. Download lcg-CA.repo, copy in /etc/yum.repos.d/ and install lcg-CA.

wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/lcg-CA.repo
yum install lcg-CA

3. Install your host certificate in /etc/grid-security

4. Download glite-APEL.repo and copy in /etc/yum.repos.d/

wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-APEL.repo

5. Install fetch-crl (if other case yaim fails)

wget http://etics-repository.cern.ch/repository/download/registered/externals/fetch-crl/2.7.0/noarch/fetch-crl-2.7.0-1.noarch.rpm
rpm -Uvh fetch-crl-2.7.0-1.noarch.rpm

6. Install glite-APEL

yum install glite-APEL

7. Change by hand the keytool link.

rm /usr/bin/keytool
ln -s /usr/java/jdk1.6.0_20/bin/keytool /usr/bin/keytool

You have to adapt the command to your path of keytool

8. Configure yaim. Only it is necessary MYSQL_PASSWORD, SITE_NAME, CE_HOST, APEL_DB_PASSWORD and MON_HOST in site-info.def (usually /opt/glite/yaim/etc/site-info.def). If you have the site-infor of your old mon, you can use it

9. Run yaim. You have to run yaim for each CE just changing CE_HOST variable in site-info.def

/opt/glite/yaim/bin/yaim -c -s /opt/glite/yaim/etc/site-info.def -n glite-APEL

10. Modify the configuration in your CE(s) to point to the new node

This can be done by either:

Modifying the MON_HOST variable in site-info.def, setting it to the new glite-APEL node, and rerunning yaim (in your CE(s)).
Check if the the APEL parser configuration file in all the CEs and batch system nodes where it is installed, have change with the new configuracion. If not, change by hand. This configuration file can be found in:

/opt/glite/etc/glite-apel-/parser-config-yaim.xml
   * The value for the mysql DBURL must be set to the new glite-APEL node:
...
jdbc:mysql://glite-apel-host:3306/accounting
...

11. Create a backup of the database in the glite-MON:

 mysqldump -u username -p accounting > mon_backup.sql

12. Stop mysqld on the glite-MON

 service mysqld stop

13. Import backup of database into the glite-APEL database

 mysql -u username -p < mon_backup.sql

14. Register your new glite-APEL node in GOCDB (as gLite-APEL, not as a MON), including the correct DN. You can get the DN in the field subject in your hostcert.pem. An example could be /DC=es/DC=irisgrid/O=cesga/CN=host/mon.ibergrid.cesga.es

15. Wait for the access list is updated. Meanwhile, if you run the cron, you will get an error like:

mié ago 11 12:28:59 UTC 2010: apel-publisher - **** Combining tables and republishing in
 ****
mié ago 11 12:28:59 UTC 2010: apel-publisher - Checking valid CPU spec data exists
mié ago 11 12:28:59 UTC 2010: apel-publisher - CPU spec values found
mié ago 11 12:29:09 UTC 2010: apel-publisher - program aborted
org.glite.apel.core.
: org.glite.apel.core.
: javax.jms.JMSException: User name or password is invalid: No user for client  certificate: CN=host/mon.ibergrid.cesga.es, O=cesga, DC=irisgrid, DC=es
       at org.glite.apel.publisher.
.(Unknown Source)
       at org.glite.apel.publisher.
.run(Unknown Source)
       at org.glite.apel.publisher.
.runJoinProcessor(Unknown Source)
       at org.glite.apel.publisher.
.run(Unknown Source)
       at org.glite.apel.publisher.
.main(Unknown Source)
Caused by: org.glite.apel.core.
: javax.jms.JMSException: User name or password is invalid: No user for client certificate: CN=host/  mon.ibergrid.cesga.es, O=cesga, DC=irisgrid, DC=es
       at org.glite.apel.publisher.
.createActiveMQProducer(Unknown Source)
       ... 5 more
....
...

References:

Index

No Pages to show