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


Ignore:
Timestamp:
Apr 21, 2011, 10:23:51 AM (13 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

    v5 v6  
    99''Note : SCDB has no http (generally Apache but not a requirement) or Subversion server version dependency.''
    1010
    11 == Installing a new SCDB Release ==
     11== Installing a new SCDB Release == #SCDBRelease
    1212
    1313To 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:
    1414 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:
     15 1. Go to the top directory of your production SCDB installation and use [/wiki/Development/Templates/RepUpdate#MergingchangefromaproductionSCDB directory-sync] to synchronize your SCDB components with the checkout done during the previous step. A typical command would be:
    1616{{{
    1717 find external utils src -type d -not -path '*.svn*' -exec /scdb/pro/utils/misc/directory-sync {} /scdb/pro \;
    1818}}}
    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):
     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 *`, any file deleted by mistake can be reverted with `svn revert`) and copy the new version of these files from the checkout done during step 1. A typical command is (ignore error message about directories):
    2020{{{
    2121cp /scdb/pro .
    2222}}}
     23 1. Check the changed files with `svn status`, revert (`svn revert`) what is not appropriate (in particular some files specific to your installation may have been deleted) and commit the new SCDB version into your production SCDB installation
    2324
    24 == Updating SCDB Tools ==
     25== Updating Individual SCDB Components ==
     26
     27=== Updating SCDB Tools ===
    2528
    2629SCDB tools is a set of utilities, underlying products and ant tasks used to manage SCDB and produce/maintain some templates. They are all maintained separately from the QWG templates and their source is in [source:SCDB SCDB branch] of QWG repository. There are 3 separate branches related to SCDB tools:
    … …  
    3437For the [source:SCDB/trunk/external external] directory in SCDB tools, which contains all external tools used by SCDB, you can use a ''SVN external reference'' rather than having them directly inside your production SCDB. Look at how this is configured in [source:SCDB/trunk/external SCDB distribution] for an example. This has the advantage of smoother and easier upgrade of this part of SCDB tools at the cost of requiring a working connection with QWG repository to be able to deploy a configuration change.
    3538
    36 === Updating with Eclipse ===
     39==== Updating with Eclipse ====
    3740
    3841In fact, there is not much to say about this. All SCDB tools are contained inside SCDB. Whether you are using Eclipse or not is not relevant but this is probably easier to update SCDB tools with command line tools on a Unix system than with a GUI. The basic operation is the same: check out the new version, copy the files it provides to your production SCDB.
    … …  
    4043If SCDB tools has been update from outside Eclipse, getting the new tools under Eclipse is just the matter of a "SVN update'. Depending on your Eclipse Java VM configuration, you may have to restart Eclipse to successfully update `panc` and use the new version (if you use the same Java VM for Eclipse and SCDB, which is generally recommended).
    4144
    42 == Updating AII ==
     45=== Updating AII ===
    4346
    4447The only Quattor specific RPMs used with SCDB are installed on Quattor server for AII support. They are :
    … …  
    5457Normally, 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.
    5558
    56 == Updating SWrep ==
     59=== Updating SWrep ===
    5760
    5861SWrep is the Quattor original service for managing RPM repositories. SCDB provides an alternative, based on plain http server and managed with SCDB Ant Tools (task `update.rep.templates`). If you want to use SCDB with SWrep, you have to also manage SWrep updates, using the standard upgrade procedure for SWrep.
    59 
    60 I