Changes between Version 5 and Version 6 of Doc/gLite/TemplateLayout


Ignore:
Timestamp:
Jul 18, 2006, 9:45:48 AM (19 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/gLite/TemplateLayout

    v5 v6  
    2525 * `common` : one directory per lower-level service used to configure high-level service.
    2626
    27 There are a few exception to the service oriented layout of templates, in `common` area :
     27There are a few exception to the service oriented layout of templates :
    2828 * `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.
    29  * `security` : this directory contains all the templates related to security configuration, mainly GSI (host certificates checking, accepted CAs, CRL management...)
     29 * `common/security` : this directory contains all the templates related to security configuration, mainly GSI (host certificates checking, accepted CAs, CRL management...)
    3030
    3131In addition, gLite templates include the following hierarchies, very close to what existed in LCG2 templates :
    … …  
    5252'''Note : don't change the name of the template, even if you change the name of the account used''' (else you'll need to modify standard templates needing this user).
    5353
     54=== Accepted CAs ===
     55
     56There is one template defining all the accepted CAs. We generally produced a new one each time there is a new release of the list of CAs officially accepted by EGEE. If you need to adjust it, create a site or cluster specific copy of `common/security/cas.tpl` in a directory `common/security`.
     57