| 6 | | Despite the change in template layout, LCG2 [wiki:Doc/LCG2/TemplateLayout template customization] is still valid for gLite3. Refer to this description, except for components with an explicit description provided here. |
| | 6 | Site customization to QWGtemplates is done through a small set of templates used to define variables used as input by QWG templates. This doesn't cover OS basic configurationt that is decribed in the page about [wiki:Doc/TemplateCustom template framework]. |
| | 7 | |
| | 8 | All site parameters related to QWG middleware are supposed to be declared in template {{{pro_lcg2_config_site.tpl}}}. A sensible default value is provided for all required variables in template source:template/trunk/grid/glite-3.0.0/defaults/site.tpl provided as part of QWG templates. This template must be included as part of the site {{{pro_lcg2_config_site.tpl}}} that must provide an explicit value for at least all the variable {{{undef}}} in template source:template/trunk/grid/glite-3.0.0/defaults/site.tpl. |
| | 9 | |
| | 10 | To ease transition from LCG2 to gLite3, the template defining default parameters can still be accessed as source:template/trunk/grid/lcg-2.7.0/sources/pro_lcg2_config_system_defaults.tpl. |
| | 11 | |
| | 12 | |
| | 13 | === Machine types === |
| | 14 | |
| | 15 | 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. |
| | 16 | |
| | 17 | To configure a specific machine with gLite 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). |
| | 18 | |
| | 19 | Here an example for configuring a Torque based CE : |
| | 20 | |
| | 21 | {{{ |
| | 22 | object template profile_grid10; |
| | 23 | |
| | 24 | # Define specific configuration for a GRIF CE to be added to |
| | 25 | # standard configuration |
| | 26 | variable CE_TORQUE_CONFIG_SITE = "pro_ce_torque_grif"; |
| | 27 | |
| | 28 | # Configure as a CE (Torque) + Site's BDII |
| | 29 | include pro_ce_torque; |
| | 30 | |
| | 31 | # |
| | 32 | # software repositories (should be last) |
| | 33 | # |
| | 34 | include repository_common; |
| | 35 | }}} |
| | 36 | |
| | 37 | In this example, {{{CE_TORQUE_CONFIG_SITE}}} specify the name of a template defining the Torque configuration. |
| | 38 | |
| | 39 | All the machine types share a common basic configuration, described in template `machine-types/base.tpl`. This template allows to add site specific configuration to this common basic configuration (e.g. configuration of a monitoring agent). This is done by defining variable {{{GLITE_BASE_CONFIG_SITE}}} to a template containing the site specific configuration to be added to the common configuration (at the end of the common configuration). This variable can be defined, for example, in template {{{pro_site_cluster_info.tpl}}}. |
| | 40 | |
| | 41 | == VO Configuration == |
| | 42 | |
| | 43 | 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. |
| | 44 | |
| | 45 | 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) : |
| | 46 | |
| | 47 | * NODE_VO_LIST (list) : define the list of VO to initialize on current node. Default : VOS variable defined in {{{pro_lcg2_config_site}}}. |
| | 48 | * NODE_VO_POOLACCOUNTS (boolean) : pool account must be created for each VO initialized. Default : true. |
| | 49 | * NODE_VO_GRIDMAPDIR_CONFIG (boolean) : gridmapdir entries must be initialized for pool accounts. Default : NODE_VO_POOLACCOUNTS variable. |
| | 50 | * 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. |
| | 51 | * NODE_VO_WLCONFIG (boolean) : initialize workload management environment for each VO. Normally enabled only on resource brokers. Default : false. |
| | 52 | * NODE_VO_CREATEHOME (boolean) : create home directories for pool accounts. Default : true. |
| | 53 | |
| | 54 | 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. |
| | 55 | |
| | 56 | Adding a new VO to standard VOs require creating 2 templates. Use an existing VO, in {{{vo}}} directory, as a template. |
| | 57 | |
