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

Timestamp:

Mar 30, 2007, 9:59:38 AM (17 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…

Comment:

--

Download/QWGTemplates/Install

@@ -34 +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.''
 
-To 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.
+To integrate new/changed templates in your configuration database, you can use the tool documented at [wiki:Development/Templates/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.
 
 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 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).
@@ -50 +50 @@
 === Controlling gLite Updates Installation ===
 
-Starting with QWG templates release [milestone:gLite-3.0.2-10 gLite-3.0.2-10], it is possible to control on a per node, per cluster or per site basis the deployment of a specific gLite update provided by QWG templates. This is done by defining variable `GLITE_UPDATE_VERSION` in a node profile, `pro_site_cluster_info.tpl` or `pro_lcg2_config_site.tpl` respectivly. The value of the variable is generally a Glite update number : in fact it needs to match a directory name under [source:templates/trunk/grid/glite-3.0.0/updates cfg/grid/glite-3.0.0/updates].
+QWG templates releases deliver the last gLite updates available at the time of the release. There is no equivalent between QWG release number (`-n`) and gLite update numbers. Sometimes one QWG templates release deliver several gLite updates. In each QWG release, there is a default associated gLite update (generally the last one).
+
+To allow site as much flexibility as possible in selecting what gLite update to install on a specific node, cluster or site, starting with QWG release 3.0.2-10, a release provides each gLite update separatly, not just the last one. You can select the gLite update you want to deploy by defining variable `GLITE_UPDATE_VERSION` at the beginning of your node profile, in `pro_site_cluster_info.tpl' or in gLite site parameters `pro_lcg2_config_site` respectively. The value specified must be a string and is generally the gLite update number : in fact it needs to match a directory name under [source:templates/trunk/grid/glite-3.0.0/updates cfg/grid/glite-3.0.0/updates].
+
+For exampple, to stay with update 15 in a specific cluster, edit `site/pro_site_cluster_info.tpl` for the cluster and add :
+{{{
+variable GLITE_UPDATE_VERSION = '15';
+}}}