Changes between Version 10 and Version 11 of Download/QWGTemplates/Install


Ignore:
Timestamp:
Mar 30, 2007, 9:46:19 AM (17 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Download/QWGTemplates/Install

    v10 v11  
    2424There are 2 methods to upgrade QWG templates, according to the structure and constraints of your site :
    2525 * In place upgrade : in this scenario, existing templates will be upgraded and the changes will be deployed on all clusters of your site. You can control the gLite updates you deploy on a per node basis.
    26  * Fresh installation of new middleware templates : this allows to control on a per cluster basis the deployement of new QWG templates.
     26 * Fresh installation of new middleware templates : this allows to control on a per cluster basis the deployement of new QWG templates. In this scenario, you are still doing an in-place upgrade of standard and OS templates.
    2727 
     28=== In-place Upgrade ===
    2829
    29 For an easy upgrade, the recommended method is :
    30  * Checkout the QWG template branch you need, in a separate area from your configuration database.
     30An in-place upgrade basically involves :
     31 * Checking out the QWG template release you need, in a separate area from your configuration database.
    3132 * Synchronize your configuration database with your local copy of QWG templates.
     33
     34''Note : you are advised to maintain an area where you have checked out QWG templates from [https://svn.lal.in2p3.fr/LCG/QWG/templates QWG repository] (never check out the whole `templates `branch` but only the version you need, [source:templates browse] through the repository to find it). This way updgrading to a new version is much more efficient : you can use `svn update` or `svn switch` to download only the changed bits.''
    3235
    3336To integrate new/changed templates in your configuration database, you can use the tool documented at [wiki:Development/RepUpdate], originally developped to do the reverse synchronization (update QWG repository from a real configuration database). This tool can be used '''only''' with [wiki:Doc/SCDB SCDB], as it relies on [http://subversion.tigris.org Subversion] to do a non destructive update. As a benefit, it cannot damage your configuration database as every change made by this tool can be reverted with Subversion.
    3437
    35 After importing all the changes with `directory-sync` (or manually), you need to commit them into your SCDB, after checking it compiles successfully and the changes in the profiles look appropriate (generally mainly some RPMS update). For this last check you can use `src/utils/profiles/compare_xml` script. After integrated the new templates, identify the changed templates, review the change if necessary and revert those not appropriate. You'll probably need to revert changes of all templates in directories `repository` (these templates are site specific but some of them are required to reside in standard directories for multiple version support).
     38After importing all the changes with `directory-sync` (or manually), you need to commit them into your SCDB, after checking it compiles successfully and the changes in the profiles look appropriate (generally mainly some RPMS update). For this last check you can use `src/utils/profiles/compare_xml` script. After integrating the new templates, identify the changed templates, review the change if necessary and revert those not appropriate. You'll probably need to revert changes of all templates in directories `repository` (these templates are site specific but some of them are required to reside in standard directories for multiple version support).
    3639
     40''Note : when checking for changes brought by a new version, you can temporaly define `GLITE_UPDATE_VERSION` to your current version. This way you should have no changed RPMs.''
     41
     42
     43=== Fresh Installation of New Middleware Templates ===
     44
     45In this scenario, you first have to download the new version of the templates, as in previous scenario. After, rather than sync'ing your templates with the release, you can copy the middleware templates provided by the release (e.g. `grid/glite-3.0.0`) in a new directory under `cfg/grid` in your CDB/SCDB and add them to the repository (use `svn add` for SCDB).
     46
     47After you can select the deployment of the new release on a per cluster basis. For this, you have to edit `cluster.build.properties` of the cluster and update the include path, replacing references to previous release of middleware templates by reference to the new one you just added.