From 8ecc7162fa5105d8e1278402ea4b7a439a388a46 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Ale=C5=A1=20K=C5=99enek?= Date: Fri, 8 Jan 2010 11:41:09 +0000 Subject: [PATCH] Migration of proxy database --- org.glite.lb.doc/src/LBAG-Installation.tex | 26 +++++++++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/org.glite.lb.doc/src/LBAG-Installation.tex b/org.glite.lb.doc/src/LBAG-Installation.tex index de54b5f..5d7994f 100644 --- a/org.glite.lb.doc/src/LBAG-Installation.tex +++ b/org.glite.lb.doc/src/LBAG-Installation.tex @@ -194,6 +194,7 @@ mysql -u lbserver lbserver20 \ \subsubsection{Migration to \LB 2.0} +\label{inst:migrate20} The migration process of existing \LB 1.x database to the \LB 2.0 is not handled automatically. The database schema change is required due to support of merged \LB server and proxy services using single @@ -357,11 +358,30 @@ disk separate from OS and MySQL log files (\texttt{innodb\_log\_group\_home\_dir \subsection{\LB proxy} \label{inst:LBproxy} -TODO: Describe LB Proxy migration here. +% TODO: Describe LB Proxy migration here. -All necessary configuration of standalone \LB proxy is done by YAIM, -previous \LB server section applies to merged server+proxy setups (\LBnew only). +All necessary configuration of \LB proxy is done by YAIM, +and described with gLite WMS installation elsewhere. +Previous \LB server section applies to merged server+proxy setups (\LBnew only). + +A~special care must be taken when an existing \LB proxy database +is migrated to \LBnew. +In general, this is not a~typical scenario -- \LBnew server in proxy mode +on WMS node is introduced with a~major WMS upgrade, and it is expeced +to be installed from scratch rather than migrated, preserving \LB proxy data. + +If the migration is really needed, \verb'glite-lb-migrate_db2version20' +script should be run with~\verb'-p' (Sect~\ref{inst:migrate20}). +However, the \LB database name remains \verb'lbproxy' while +the \LBnew binaries expect unified \verb'lbserver20' by default. +Because renaming a~MySQL database is a~non-trivial, error prone task, +the recommended workaround is to add the following variable setting + +\verb'GLITE_LB_SERVER_OTHER_OPTIONS="--mysql lbserver/@localhost:lbproxy"' + +into the gLite startup environment (\verb'/opt/glite/etc/profile.d') instead. +This setting makes \LB server use the \verb'lbproxy' database instead of the default. \subsection{\LB logger} -- 1.8.2.3