Changes between Version 7 and Version 8 of Doc/LCG2/TemplateLayout

Timestamp:

Apr 7, 2006, 10:14:22 PM (20 years ago)

Author:

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

Comment:

--

Doc/LCG2/TemplateLayout

@@ -33 +33 @@
 
 
-=== Cluster parameters ===
+=== Machine types ===
 
-For every cluster, it is possible to customize configuration in template {{{pro_site_cluster_info.tpl}}}. As a general rule, you need to define the following properties for each cluster (value mentionned are just examples) :
+QWG templates provide a template per machine type (CE, SE, RB, ...). They are located in {{{machine-types}}} directory and are intended to be generic templates. No modification should be needed.
+
+To configure a specific machine with LCG2 middleware, you just need to include the appropriate machine type template into the machine profile, after specifying a template containing the specific configuration for this particular machine with the variable {{{xxx_CONFIG_SITE}}} (look in the template for the exact name of the variable). 
+
+Here an example for configuring a Torque based CE : 
 
 {{{
+object template profile_grid10;
+
+# Define specific configuration for a GRIF CE to be added to
+# standard configuration
+variable CE_TORQUE_CONFIG_SITE = "pro_ce_torque_grif";
+
+# Configure as a CE (Torque) + Site's BDII
+include pro_ce_torque;
+
 #
-# basic site information
+# software repositories (should be last)
 #
-"/system/cluster/name" = "LCG 2.7.0";
-"/system/cluster/type" = "batch";
-"/system/state" = "production";
-"/system/siterelease" = "SL 3.05";
-"/system/rootmail" = "grid.support@lal.in2p3.fr";
+include repository_common;
 }}}
 
-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 :
-{{{
-FILESYSTEM_CONFIG_SITE = "pro_lcg2_system_filesystems";
-}}}
+In this example, {{{CE_TORQUE_CONFIG_SITE}}} specify the name of a template defining the Torque configuration.
 
+For DPM SE servers, there is an additional variable, {{{SEDPM_SRM_SERVER}}}, that must be defined to {{{true}}} on the DPM master node. Also, if you are not using a MySQL database, you need to define variable {{{SEDPM_DB_TYPE}}} to {{{oracle}}}.
 
 === VO Configuration ===
@@ -58 +65 @@
 VO configuration consists to define variable {{{VOS}}} in {{{pro_lcg2_config_site.tpl}}}. This variable can also be redefined in the context of a specific node, if {{{pro_lcg2_config_site.tpl}}} defines {{{VOS}}} as a default value.
 
+VO configuration is done by template {{{vo/pro_vo_config.tpl}}}. Behaviour of this template can be customized with variables. Main variables are (see the template for the full list) :
+
+ * NODE_VO_LIST (list) : define the list of VO to initialize on current node. Default :  VOS variable defined in {{{pro_lcg2_config_site}}}.
+ * NODE_VO_POOLACCOUNTS (boolean) : pool account must be created for each VO initialized. Default : true.
+ * NODE_VO_GRIDMAPDIR_CONFIG (boolean) : gridmapdir entries must be initialized for pool accounts. Default : NODE_VO_POOLACCOUNTS variable.
+ * NODE_VO_SITE_CONFIG (string) : site specific template that must be included before actually doing VO intialization. Allow for specific VO modification to default VO configuration.Default : none.
+ * NODE_VO_WLCONFIG (boolean) : initialize workload management environment for each VO. Normally enabled only on resource brokers. Default : false.
+ * NODE_VO_CREATEHOME (boolean) : create home directories for pool accounts. Default : true.  
+
+Templates defining machine types define these variables to the value appriated for a given machine type and there should be normally no need to define these variables.
+
 Adding a new VO to standard VOs require creating 2 templates. Use an existing VO, in {{{vo}}} directory, as a template.
+