Changes between Version 5 and Version 6 of Doc/TemplateCustom

Timestamp:

Jun 8, 2006, 9:12:58 AM (19 years ago)

Author:

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

Comment:

--

Doc/TemplateCustom

@@ -11 +11 @@
  * Preserve site customization across software upgrades (OS or middleware)
  * Allow support of several sites sharing some configuration database, leveraging overall management load but keeping required flexibility.
+
+'''Note : QWG Templates, starting with release 2.7.0-7, require PAN compiler 5.0.4 or later.'''
 
 == Template Hierarchies ==
@@ -83 +85 @@
 }}}
 
+=== Selecting OS version ===
+
+There are 2 possibilities to select the OS version used by a cluster or a specific node :
+
+ * Define the OS version at the OS level : this is done by adding the appropriate path in {{{cluster.build.properties}}}. Look at the example above, in section [[wiki:DOC/TemplateCustom#ClustersandTemplateHierarchies Clusters and Template Hierarchies]]. Using this method, all the machines in the cluster MUST run the same OS version/architecture. This is the only method available for SL versions before SL 4.2.
+ * Define the OS version at the machine level : this is done by defining the appropriate PAN {{{loadpath}}} in the machine template. A cluster default can be defined in {{{pro_site_cluster_info.tpl}}} and a specific setting can be define in a machine profile to override this default. A template for OS selection is provided in LCG2 templates, in directory {{{os}}} (there is one template per OS version/architecture). This method allows to have different version/architecture combination into the same cluster. This is the recommended method for any cluster running SL4.
+
+This second method requires OS template path in {{{cluster.build.properties}}} to be defined as {{{os}}} instead of the hierarchy used in first method.
+
+Both methods can also be combined by specifying OS template path as follow in {{{cluster.build.properties}}} :
+{{{
+os os/sl305-i386/**/*
+}}}
+
+With these entries, the cluster will use SL 3.05 i386 as the default OS version for the cluster but this is possible to override this in any machine templates, using the second method. This is the only possibility to have both SL3 and SL4 in the same cluster, as SL3 templates don't support the second method.
+
+
 === RPM repositories ===