Changes between Version 6 and Version 7 of Doc/TemplateCustom

Timestamp:

Jun 8, 2006, 9:14:27 AM (18 years ago)

Author:

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

Comment:

--

Doc/TemplateCustom

@@ -89 +89 @@
 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 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.