Changes between Version 12 and Version 13 of Download/QWGTemplates/Install


Ignore:
Timestamp:
Mar 30, 2007, 9:53:21 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

    v12 v13  
    1919Standard templates are made of 3 areas (see [wiki:Doc/TemplateCustom template layout]) :
    2020 * OS templates : they are never modified, except for fixes. The only modifications apply to errata RPM list. These errata are not installed by default.
    21  * Middleware templates (if using them) : they bring both changes and fixes at each release. They are intended to be backward compatible : that means the resulting configuration should be the same if you don't change your local configuration. As part of QWG releases, they deliver gLite updates : `GLITE_UPDATE_VERSION` allows to control deployment of gLite updates as part of QWG templates update.
     21 * Middleware templates (if using them) : they bring both changes and fixes at each release. They are intended to be backward compatible : that means the resulting configuration should be the same if you don't change your local configuration. As part of QWG releases, they deliver gLite updates : [wiki:Download/QWGTemplates/Install#ControllinggLiteUpdatesInstallation GLITE_UPDATE_VERSION] allows to control deployment of gLite updates as part of QWG templates update.
    2222 * Standard templates : all modifications in this area are entirely backward compatible
    2323
    2424There are 2 methods to upgrade QWG templates, according to the structure and constraints of your site :
    25  * 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.
     25 * 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 [wiki:Download/QWGTemplates/Install#ControllinggLiteUpdatesInstallation control] the gLite updates you deploy on a per node basis.
    2626 * 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 
    … …  
    3838After 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).
    3939
    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.''
     40''Note : when checking for changes brought by a new version, you can temporaly define [wiki:Download/QWGTemplates/Install#ControllinggLiteUpdatesInstallation GLITE_UPDATE_VERSION] to your current version. This way you should have no changed RPMs.''
    4141
    4242