Changes between Version 14 and Version 15 of Doc/gLite/TemplateLayout


Ignore:
Timestamp:
Feb 10, 2011, 9:29:27 AM (13 years ago)
Author:
/C=UK/O=eScience/OU=CLRC/L=RAL/CN=richard hellier
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/gLite/TemplateLayout

    v14 v15  
    66This page contains a description of the layout of templates for gLite provided by QWG and how the site customization should be integrated. See page on template [wiki:Doc/TemplateCustom framework]  for more details on template framework structure and site customization.
    77
    8 Layout of gLite templates is based on PAN namespaces. This PAN feature brings an improved manageability. Among advantages, it allows :
     8Layout of gLite templates is based on PAN namespaces. This PAN feature brings improved manageability. Among the advantages, it allows :
    99 * More structured layout
    10  * Easier guess of where a template is located as its relative path is part of its name
     10 * Easier to guess where a template is located as its relative path is part of its name
    1111
    1212gLite templates are organized per ''service''. There are 3 categories of services, described in 3 different directories :
    … …  
    1515 * `common` : one directory per lower-level service (nfs, ssh, ...) used to configure high-level service.
    1616
    17 There are a few exception to the service oriented layout of templates :
    18  * `users` : to improve consistency in account IDs allocation, all the account related templates (user/group creation) arenow in one directory, `common/users`, and is no longer part of service information. There is one template per user/group and the name of this template is generally the name of the user created. Some of them are empty : they are just placeholders to allow a site to define this accout.
     17There are a few exceptions to the service-oriented layout of templates :
     18 * `users` : to improve consistency in account IDs allocation, all the account related templates (user/group creation) are now in one directory, `common/users`, and are no longer part of service information. There is one template per user/group and the name of this template is generally the name of the user created. Some of them are empty : they are just placeholders to allow a site to define this account.
    1919 * `common/security` : this directory contains all the templates related to security configuration, mainly GSI (host certificates checking, accepted CAs, CRL management...)
    2020
    … …  
    2727
    2828Inside each service directory, template names are quite standardized. Main templates, available in every service where it is relevant, are :
    29  * `rpms/arch/config.tpl` : contains all the RPMs required to run the service on the corresponding OS architecture (in gLite 3.0 templates where there was only one architecture supported, the corresponding template as `rpms.tpl`.
     29 * `rpms/arch/config.tpl` : contains all the RPMs required to run the service on the corresponding OS architecture (in gLite 3.0 templates where there was only one architecture supported, the corresponding template was `rpms.tpl`).
    3030 * `service.tpl` : contains all middleware components that need to be configured to run a specific service. This is mainly used for high level services, like CE, WN, BDII... This doesn't include any OS related information.
    3131 * `config.tpl` : contains all the configuration information required to configure the service itself (but not the included services). This template is generally responsible for including the relevant RPMs related templates.