Difference: VomsTestsP3407 (29 vs. 30)

Revision 302010-03-23 - ElisabettaMolinari

Line: 1 to 1

Certification report patch 3407

Author: Elisabetta Molinari elisabetta.molinari@mi.infn.it

Line: 128 to 128

Upgrade from production

Changed:

<
<

Since this is the first release of VOMS for SL5, only the upgrade of the mysql backend has been tested. Following the basic steps:
- Dump the old database on the old VOMS server and transfer the file to the new node as in the following:
```
 mysqldump -h <OLD_HOSTNAME> -u <USER> -p --databases <DB_NAME> > <DUMP_FILE>
```
- Use the database dump on the new machine to create the new database as in the following:
```
mysql -h <NEW_HOSTNAME> -u <PRIV_USER> -p < <DUMP_FILE>
```
- make sure the mysql db on the new machine accepts external connections by doing the following for ex.:
```
grant all on *.* to 'root'@'voms-rd02-21.cnaf.infn.it' identified by 'admin';
```
- for each VO database you want to upgrade launch the following:
```
/opt/glite/sbin/voms-admin-configure --vo <VO_NAME> --dbhost <remote_host_name> upgrade
```

>
>

Since this is the first release of VOMS for SL5, only the upgrade of the mysql backend has been tested. Following the basic steps of a sample upgrade:

- dump the old database  on the old VOMS server and transfer the file to the new node: mysqldump -h <OLD_HOSTNAME> -u <USER> -p --databases <DB_NAME> > <DUMP_FILE>
- mysql -u root -p < dbsa3test; mysql -u root -p < dbvomstest;
- grant all on *.* to 'root'@'voms-rd02-21.cnaf.infn.it' identified by 'admin';
- grant all on db_sa3test.* to 'sa3test_user'@'voms-rd02-21.cnaf.infn.it' identified by 'admin';
- grant all on db_sa3test.* to 'sa3test_user'@'localhost' identified by 'admin';
- grant all on db_vomstest.* to 'vomstest_user'@'voms-rd02-21.cnaf.infn.it' identified by 'admin';
- grant all on db_vomstest.* to 'vomstest_user'@'localhost' identified by 'admin';
- synchronize yaim conf files from the old machine with the new one, i.e. make sure username and password for the VO databases are the same 
- launch yaim configuration after setting yaim variable  VOMS_DB_DEPLOY to 'false' in the siteinfo.def or the services/glite-voms file
- re-start tomcat
- launch upgrade VO, for each VO as in the following: /opt/glite/sbin/voms-admin-configure upgrade --vo=sa3test
- register the VOMS host identity as a default admin  -->/opt/glite/sbin/voms-db-deploy.py add-admin --vo sa3test --cert /etc/grid-security/hostcert.pem

here's an upgrade log

Check Bugs:

Line: 236 to 244

yaimlog: yaim configuration log

Added:

>
>

upgrade_log.gz: upgrade log

META FILEATTACHMENT	attachment="full_result.html.gz" attr="" comment="full result voms admin report" date="1268901414" name="full_result.html.gz" path="full_result.html.gz" size="2290" stream="full_result.html.gz" tmpFilename="/usr/tmp/CGItemp8918" user="ElisabettaMolinari" version="1"
META FILEATTACHMENT	attachment="full_result_vomscore.html.gz" attr="" comment="full result voms core report" date="1268901542" name="full_result_vomscore.html.gz" path="full_result_vomscore.html.gz" size="4027" stream="full_result_vomscore.html.gz" tmpFilename="/usr/tmp/CGItemp8694" user="ElisabettaMolinari" version="1"
META FILEATTACHMENT	attachment="yum_install_log.gz" attr="" comment="yum install log" date="1268922254" name="yum_install_log.gz" path="yum_install_log.gz" size="2427" stream="yum_install_log.gz" tmpFilename="/usr/tmp/CGItemp8790" user="ElisabettaMolinari" version="1"
META FILEATTACHMENT	attachment="yaimlog" attr="" comment="yaim configuration log" date="1268924986" name="yaimlog" path="yaimlog" size="34085" stream="yaimlog" tmpFilename="/usr/tmp/CGItemp8790" user="ElisabettaMolinari" version="1"

Added:

>
>

META FILEATTACHMENT	attachment="upgrade_log.gz" attr="" comment="upgrade log" date="1269336569" name="upgrade_log.gz" path="upgrade_log.gz" size="2104" stream="upgrade_log.gz" tmpFilename="/usr/tmp/CGItemp13242" user="ElisabettaMolinari" version="1"

View topic | History: r34 < r33 < r32 < r31 | More topic actions...