Changes between Version 4 and Version 5 of Obsolete/Download/SCDB/Upgrade


Ignore:
Timestamp:
Apr 21, 2011, 10:12:09 AM (15 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Obsolete/Download/SCDB/Upgrade

    v4 v5  
    55
    66
    7 SCDB consists mainly in a set of client side tools, a Subversion server and an http server. Thus SCDB upgrades mainly consist of updating SCDB tools. In addition there a few Quattor specific RPMs on the Quattor server used for AII (initial installation of machines). This page describes how to upgrade each SCDB and Quattor specific parts. Refer to the relevant product documentation if you want to upgrade your http or Subversion server.
     7SCDB consists mainly in a set of client side tools, a Subversion server and an http server. Thus SCDB upgrades mainly consist of updating SCDB tools, Pan compiler and a few other external tools packages with SCDB (in `external` directory). In addition there a few Quattor specific RPMs on the Quattor server used for AII (initial installation of machines). This page describes how to upgrade each SCDB and Quattor specific parts. Refer to the relevant product documentation if you want to upgrade your http or Subversion server.
    88
    99''Note : SCDB has no http (generally Apache but not a requirement) or Subversion server version dependency.''
    1010
     11== Installing a new SCDB Release ==
     12
     13To help upgrading all SCDB components and keeping them in sync, periodically [/wiki/ReleaseNotes/SCDB#Releases SCDB releases] are produced. Upgrading SCDB components of a production Quattor installation to a new SCDB releases involves a few steps:
     14 1. Do a fresh checkout of the [/wiki/ReleaseNotes/SCDB#Releases SCDB release] you want to install. The last recommended release is available at SVN URL  http://svn.lal.in2p3.fr/LCG/QWG/SCDB/tags/pro. Note that this URL can be checked out but that a working copy referring this URL cannot be updated. In examples provided below, we assume this checkout is available in `/scdb/pro`: replace by the actual path at your site.
     15 1. Go to the top directory of your production SCDB installation and use directory-sync to synchronize your SCDB components with the checkout done during the previous step. A typical command would be:
     16{{{
     17 find external utils src -type d -not -path '*.svn*' -exec /scdb/pro/utils/misc/directory-sync {} /scdb/pro \;
     18}}}
     19 1. Remove all the plain files located in the top directory of your production installation except `quattor.build.properties` (this can be done with `rm *`) and copy the new version of these files from the checkout done during step 1. A typical command is (ignore error message about directories):
     20{{{
     21cp /scdb/pro .
     22}}}
    1123
    1224== Updating SCDB Tools ==
    … …  
    4052These RPMs may have some other non Quattor-specific dependencies.
    4153
    42 Other parts of SCDB have no dependency on these RPMs and they can be freely updated as needed, when new versions of these RPMs become available.
     54Normally, the recommended version for these RPMs is configured by default through standard template [source:/templates/trunk/standard/quattor/aii/server/rpms.tpl standard/quattor/aii/server/rpms.tpl].  As other parts of SCDB have no dependency on these RPMs and they can be freely updated as needed, when new versions of these RPMs become available.
    4355
    4456== Updating SWrep ==