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

Timestamp:

Jul 18, 2006, 9:40:19 AM (18 years ago)

Author:

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

Comment:

--

Doc/gLite/TemplateLayout

@@ -25 +25 @@
  * `common` : one directory per lower-level service used to configure high-level service.
 
+There are a few exception to the service oriented layout of templates, in `common` area :
+ * `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.
+ * `security` : this directory contains all the templates related to security configuration, mainly GSI (host certificates checking, accepted CAs, CRL management...)
+
 In addition, gLite templates include the following hierarchies, very close to what existed in LCG2 templates :
  * `machine-types` : one template per machine type. Intended to be included in a machine profile.
@@ -31 +35 @@
  * `components` : description of NCM components related to gLite services used in other gLite templates (doesn't include OS related components)
  * `defaults` : templates providing sensible default values, mainly `site.tpl' for default site parameter values.
+ * `repository` : template defining RPM repositories where gLite RPMs are located. '''Need to be edited to match site repository names.'''.
 
-To improve consistency in account IDs allocation, all the account related templates (user/group creation) is now 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.
+
 
 
@@ -38 +43 @@
 
 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.
+
+=== Allocation of Service Accounts ===
+
+Some services allow to define a specific account to be used to run the service. In this case, there is one template for each of these accounts in `common/users`. The name of the template generally matches the user account created or, when the template is empty, the name of the service.
+
+A site can redefine account names or characteristics (uid, home directory...). To do this, you should not edit directly the standard templates as the changes will be lost in the next version of the template (or you will have to redo them by hand). You should create a `users` directory somewhere in your site or cluster hierarchy (e.g. under the `site` directory, not directly at the same level else it will not work without adjusting `cluster.build.properties`) and put your customized version of the template here.
+
+'''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).
+