Voms gLite 3.2 Upgrade Guide
Install a VOMS mysql SL5 node
The general steps for installing the OS and the gLite-VOMS mysql server are explained
here.
For VOMS mysql install
only the rpms
without launching yaim configuration
Migrating the database to the new node
To migrate the VO database to the new node you need to perform the following steps, for each VO DB:
- Dump the old database on the old VOMS server and transfer the file to the new node
mysqldump -h <OLD_HOSTNAME> -u <PRIV_USER> -p <PWD> --databases <DB_NAME> > <DUMP_FILE>
- Use the database dump on the new machine to create the new database
mysql -h <NEW_HOSTNAME> -u <PRIV_USER> -p <PWD> < <DUMP_FILE>
- Grant ALL PRIVILEGES to the user that VOMS-ADMIN will use to connect to and use the database
mysql -h <NEW_HOSTNAME> -u <PRIV_USER> -p <PWD>
mysql> GRANT ALL PRIVILEGES ON <DATABASE_NAME>
TO <VOMS_USER>@localhost
IDENTIFIED BY '<VOMS_USER_PASSWORD>';
- synchronize voms configuration files from the old machine with the yaim configuration files on the new one, i.e. make sure username and password for the VO databases are the same. In particular:
- launch yaim configuration after setting yaim variable VOMS_DB_DEPLOY to 'false' in the site-info.def or the siteinfo/services/glite-voms file
/opt/glite/yaim/bin/yaim -c -s site-info.def -n VOMS
- re-start tomcat
- launch upgrade VO, for each VO as:
voms-admin-configure upgrade --vo <VO name>
- re-start voms server and voms admin with
/opt/glite/etc/init.d/voms and /opt/glite/etc/init.d/voms-admin
- register the VOMS host identity as a default admin:
/opt/glite/sbin/voms-db-deploy.py add-admin --vo <VO name> --cert /etc/grid-security/hostcert.pem
--
ElisabettMolinari - 23-Mar-2010