Page History
...
The CMT RM Perl scripts uses the MySQL client library indirectly via the Perl module PBI, and the MySQL driver DBD::mysql. On Linux everything we require is already installed and on rhel5 or rhel6 machines will be using MySQL 5.0 or newer client library. We need to check whether jobs on Windows also depend on the client library (likely yes) and, if so, whether a newer version needs to be installed and tested.On Windows we're currently using a MySQL 4.1.22 client which at some point will need to be upgraded, but not urgently (should still work with the newer server).
~glastrm/mysql-proxy might be relevant.
Testing steps
Just a proposal; by no means the final word!
- Make copies of cgi scripts used for web pages which point to copied db on mysql-node01. Verify that all functions still work.
- Make an alternate module to DBConf.pm which points to mysql-node01 (but leave the original intact).
- As much as possible, isolate parts of CMT RM which access db and test. That is, make alternate scripts which point at the alternate DBConf.pm and run them by hand.
- Make a copy of installer script(s) pointed to mysql-node01 and test.
- Full system test of the RM with mysql-node01. That is
- warn everyone not connected with testing to avoid any activity which would involve writing to db (e.g., tagging)
- shut of CMT RM
- save original DBConf.pm; rename alternate to DBConf.pm. If there are any other sources of host name besides DBConf.pm adjust those as well.
- Turn CMT RM on. Verify functionality (LATEST tag, release tag, etc.)
- Turn off CMT RM again; point everything back to glastDB; turn back on.
- The actual move:
- send general warning. There should be no tagging during the move at the very least.
- shut off RM.
- dump databases on glastDB, refresh copies on mysql-node01
- point glastDB alias to mysql-node01
- restart everything; issue all-clear
Reference
Perl and MySQL
http://search.cpan.org/~capttofu/DBD-mysql-3.0002/lib/DBD/mysql.pm
...
Overview
Content Tools