Page History

...

1. Make copies of cgi scripts used for web pages which point to copied db on mysql-node01. Make an alternate module to DBConf.pm which points to mysql-node01 (but leave the original intact). Verify that all functions still work. All ReleaseManager pages have been cloned and directed to mysql-node01; they seem ok.
2. Compare glastDB and mysql-node1 tables via command-line mysql client program. Done. There is one potentially troublesome issue: use of reserved word trigger as table name.
3. 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. Other than confirming with test script that quoting trigger in Perl usage would satisfy MySQL 5.5, did not pursue this.
4. Fix any problems found up to this point. Changed a few lines in Workflow.pm.
5. Make a copy of installer script(s) pointed to mysql-node01 and test.  
6. Full system test of the RM with mysql-node01.  That is  ##
   1. warn everyone not connected with testing to avoid any activity which would involve writing to db (e.g., tagging)
   2. shut of CMT RM
   3. 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.
   4. Turn CMT RM on.  Verify functionality (LATEST tag, release tag, etc.)
   5. Turn off CMT RM again; point everything back to glastDB; turn back on.
7.   The actual move:
   1. send general warning.  There should be no tagging during the move at the very least.
   2. shut off RM.
   3. dump databases on glastDB, refresh copies on mysql-node01
   4. point glastDB alias to mysql-node01  (did we receive confirmation that we will retain the glastDB alias?)
   5. restart everything; issue all-clear

...