Changes between Version 11 and Version 12 of Doc/TemplateCustom


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

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/TemplateCustom

    v11 v12  
    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. Using this method allows to define a default OS version for the cluster.
     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 3.07 or SL 4.2. Using this method allows to define a default OS version for the cluster.
    9292 * 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 An example of `pro_os_version_db.tpl` template is :
    95 {{{
    96 unique template pro_os_version_lal_db;
    97 
    98 variable OS_VERSION = nlist(
    99   escape("auger11.lal.in2p3.fr"),       "sl430-x86_64",
    100   escape("d03.lal.in2p3.fr"),           "sl307-i386",
    101 );
    102 }}}
     94An example of `pro_os_version_db.tpl` template can be found in the [browser/templates/trunk/sites/example/site/pro_os_version_db_lcg.tpl examples] provided in the repository. If you want to use another name for this template, you need to define variable NODE_OS_VERSION_DB in cluster `pro_site_cluster_info.tpl` template or in site `pro_site_global_variables.tpl` template. Look at [browser/templates/trunk/clusters/example/site/pro_site_cluster_info.tpl examples] provided with QWG template releases.
    10395
    10496Both methods can also be combined by specifying OS template path as follow in {{{cluster.build.properties}}} :
    10597{{{
    106 os os/sl305-i386/**/*
     98os os/sl307-i386
    10799}}}
    108100
    109 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.
     101With these entries, the cluster will use SL 3.07 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.
    110102
    111103