18 | | * 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.3. Using this method allows to define a default OS version for the cluster. |
19 | | |
20 | | An [browser:templates/trunk/sites/example/site/pro_os_version_lcg_db.tpl example] of such a template can be found in the site example provided with QWG templates. To use this ability to define OS version/architecture per machine, you '''MUST''' 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. You can provide a separate template for each cluster or share this template between several clusters. |
21 | | |
22 | | Both methods can also be combined by specifying OS template path as follow in {{{cluster.build.properties}}} : |
23 | | {{{ |
24 | | os os/sl307-i386 |
25 | | }}} |
26 | | |
27 | | With 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. |
| 18 | ''Note : if you need to use `sl305-i386` in your cluster, it '''must be''' defined as the default version for the cluster in [source:templates/trunk/cluster/examples/cluster.build.properties cluster.build.properties], adding `os/sl305-i386` '''after''' `os`.'' |
31 | | * Define the OS version at the machine level : this is done by creating a template pointed by variable NODE_OS_VERSION_DB 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. |
| 22 | Each machine in a cluster can run its own OS version/arch, different from the cluster default version. |
| 23 | |
| 24 | Tis done by creating a template pointed by variable `NODE_OS_VERSION_DB` in your site or cluster hierarchy. This variable is generally defined in cluster specific [source:templates/trunk/clusters/example/site/pro_site_cluster_info.tpl pro_site_cluster_info.tpl]. |
| 25 | |
| 26 | The template pointed to by `NODE_OS_VERSION_DB` must define variable `OS_VERSION`. This variable 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. |
| 27 | |
| 28 | ''Note : it is not possible to select `sl305-i386` as a node specific OS version. See previous section.`` |