Changes between Version 26 and Version 27 of Doc/TemplateCustom


Ignore:
Timestamp:
Jun 27, 2007, 8:27:34 AM (17 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/TemplateCustom

    v26 v27  
    2626 * [source:templates/trunk/clusters clusters] : this hierarchy is used for cluster specific templates. There should be one sub-hierarchy per ''cluster''. A ''cluster'' defines a group of machines sharing some common configuration. One specific of a cluster is that it '''must''' contain a directory {{{profiles}}} containing the machine profiles (e.g. {{{object template}}} used to define a machine configuration). It is valid for a cluster to have an empty {{{profiles}}} directory. Look at a [source:templates/trunk/clusters/example cluster example].
    2727
    28 Other pages describe in more details layout of [wiki:Doc/OS/TemplateLayout OS templates] and [wiki:Doc/gLite/TemplateLayout gLite templates].
     28Other pages describe in more details layout and customization of [wiki:Doc/OS OS templates] and [wiki:Doc/gLite gLite templates].
    2929
    3030== Clusters and Template Hierarchies ==
    … …  
    4444=== Cluster parameters ===
    4545
    46 For every cluster, it is possible to customize its configuration in template {{{pro_site_cluster_info.tpl}}}. There '''must be''' one such template per cluster. As a general rule, you need to define the following properties for each cluster (value mentionned are just examples) :
     46For every cluster, it is possible to customize its configuration in template [source:templates/trunk/clusters/example/pro_site_cluster_info.tpl pro_site_cluster_info.tpl]. There '''must be''' one such template per cluster. Look at [source:templates/trunk/clusters/example/pro_site_cluster_info.tpl example] provided for more information about the minimum set of variables to define.
    4747
    48 {{{
    49 #
    50 # basic site information
    51 #
    52 "/system/cluster/name" = "LCG 2.7.0";
    53 "/system/cluster/type" = "batch";
    54 "/system/state" = "production";
    55 "/system/siterelease" = "SL 3.05";
    56 "/system/rootmail" = "grid.support@lal.in2p3.fr";
    57 }}}
    58 
    59 You can also define variable {{{FILESYSTEM_CONFIG_SITE}}} as an alternative template name containing a filesystem layout for the cluster (or node if this is in a machine profile). For example :
    60 {{{
    61 FILESYSTEM_CONFIG_SITE = "pro_lcg2_system_filesystems";
    62 }}}
    63 
    64 {{{pro_site_cluster_info.tpl}}} is often used to define the default root password in a cluster. This can be done with the following PAN instructions :
    65 
    66 {{{
    67 #
    68 # set root password on machines
    69 #
    70 include pro_software_component_accounts;
    71 "/software/components/accounts/rootpwd" = default("$1$57qRuCXe$NPngMkg4BrPBf5hfJzJh21");
    72 "/software/components/accounts/shadowpwd" = true;
    73 }}}
    74 
    75 The encrypted password value must be provided. It can be obtained with the following command :
     48One information required is the default root password for nodes in the cluster (it can also be customized on a per node basis, into the node profile). This must be the password hash as returned by command :
    7649{{{
    7750openssl passwd -1 my_preferred_password