Changes between Initial Version and Version 1 of Doc/OS/Customization

Timestamp:

Dec 5, 2006, 10:06:22 AM (19 years ago)

Author:

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

Comment:

--

Doc/OS/Customization

@@ +1 @@
+= Configuring OS Templates =
+[[TracNav]]
+
+[[TOC(inline)]]
+
+This pages describes the use of QWG templates to configure the OS. These templates are not related to the middleware and can be used in other contexts. They are in charge of installing the required RPMs, based on feature groups requested, and do the base machine configuration (network, ...). They are used by middleware templates configuring a specific middleware machine type to do the base configuration of the machine.
+
+Look at nformation about [wiki:Doc/OS/Layout layout] of OS templates for more information.
+
+== Selecting OS version ==
+
+=== Cluster Default OS Version ===
+
+A default OS version can be associated with a cluster. When defined, unless specified otherwise (see next section), all machines will us this OS version.
+
+There are 2 possibilities to define the default OS version :
+
+ * 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.
+
+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.
+
+Both methods can also be combined by specifying OS template path as follow in {{{cluster.build.properties}}} :
+{{{
+os os/sl307-i386
+}}}
+
+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.
+
+=== Per Machine OS Version ===
+
+ * 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.
+
+== Selecting Kernel Version ==
+
+Normally, standard templates provide an appropriate definition of the kernel number and variant (smp, hugemem...) according to hardware present (as declared in templates). If you want to override this default (used in particular to configure Grub), you can use the following variables :
+
+ * `KERNEL_VERSION_NUM` : this must contain the kernel version, as it is in the RPM name, without the architecture.
+ * `KERNEL_VARIANT` : `smp`, `hugemem`, `largesmp`... or nothing (empty string) for non smp kernel. 
+
+
+== Selecting Kernel Architecture ==
+
+Normally, an attempt is made to guess the OS architecture from the CPU model. But this doesn't fit all situations, in particular with processors that can be installed as 32-bit or 64-bit. You can force the architecture you want to use on a specific machine by défining variable `CPU_ARCH` to the architecture name, using standard architecture names used in RPMs (e.g. i386, x86_64...).