Changes between Version 10 and Version 11 of Doc/TemplateCustom


Ignore:
Timestamp:
Oct 15, 2006, 10:41:08 PM (19 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/TemplateCustom

    v10 v11  
    8989There are 2 possibilities to select the OS version used by a cluster or a specific node :
    9090
    91  * Define the OS version at the cluster 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.
    92  * 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.
     91 * Define the OS version at the cluster 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. Using this method allows to define a default OS version for the cluster.
     92 * Define the OS version at the machine level : this is done by creating a template `pro_os_version_db.tpl` in your site or cluster hierarchy. In this template, variable `OS_VERSION` must contain one entry for each machine that is not using the default OS version defined for the cluster. The value is the directory containing templates for the OS version. This method allows to have different version/architecture combination into the same cluster. This second method requires OS template path in {{{cluster.build.properties}}} to be defined as {{{os}}} instead of the hierarchy used in first method.
    9393
    94 This second method requires OS template path in {{{cluster.build.properties}}} to be defined as {{{os}}} instead of the hierarchy used in first method.
     94An example of `pro_os_version_db.tpl` template is :
     95{{{
     96unique template pro_os_version_lal_db;
     97
     98variable OS_VERSION = nlist(
     99  escape("auger11.lal.in2p3.fr"),       "sl430-x86_64",
     100  escape("d03.lal.in2p3.fr"),           "sl307-i386",
     101);
     102}}}
    95103
    96104Both methods can also be combined by specifying OS template path as follow in {{{cluster.build.properties}}} :