Changes between Version 24 and Version 25 of Doc/TemplateCustom

Timestamp:

Jun 27, 2007, 8:20:30 AM (18 years ago)

Author:

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

Comment:

--

Doc/TemplateCustom

@@ -23 +23 @@
  * [source:templates/trunk/grid grid] : this hierarchy is used for templates related to EGEE/LCG middleware installation and configuration. Generally this hierarchy is made of one sub-hierarchy per middleware version (e.g. [source:templates/trunk/grid/glite-3.0.0 glite-3.0.0], [source:templates/trunk/grid/glite-3.1 glite-3.1]). This hierarchy typically contains templates provided by QWG LCG. Most of these templates are configurable through variable definition and should require no edit.
  * [source:templates/trunk/standard standard] : this hierarchy is used for other kind of standard templates provided by some products, e.g. [source:templates/trunk/standard/quattor Quattor core templates], [source:templates/trunk/standard/pan pan standard templates], [source:templates/trunk/standard/monitoring/lemon Lemon templates]... Generally this hierarchy contains one directory tree for each product. The templates in this hierarchy should not be edited.
- * [source:templates/trunk/sites sites] : this hierarchy is used for templates that are not standard (site specific templates or site customized version of standard templates) but are (potentially) common to several clusters. This hierarchy generally contains one sub-hierarchy per ''site''. ''site'' concept is explained in more detail later but has no requirement to be linked to a physical location. Look at a[source:templates/trunk/sites/example site example].
- * [source:templates/trunk/clusters clusters] : this hierarchy is used for cluster specific templates. There should be one sub-hierarchy per ''cluster''. A ''cluster'' defines a group of machines sharing some common configuration. One specific of a cluster is that it '''must''' contain a directory {{{profiles}}} containing the machine profiles (e.g. {{{object template}}} used to define a machine configuration). It is valid for a cluster to have an empty {{{profiles}}} directory. Look at a[source:templates/trunk/clusters/example cluster example].
+ * [source:templates/trunk/sites sites] : this hierarchy is used for templates that are not standard (site specific templates or site customized version of standard templates) but are (potentially) common to several clusters. This hierarchy generally contains one sub-hierarchy per ''site''. ''site'' concept is explained in more detail later but has no requirement to be linked to a physical location. Look at a [source:templates/trunk/sites/example site example].
+ * [source:templates/trunk/clusters clusters] : this hierarchy is used for cluster specific templates. There should be one sub-hierarchy per ''cluster''. A ''cluster'' defines a group of machines sharing some common configuration. One specific of a cluster is that it '''must''' contain a directory {{{profiles}}} containing the machine profiles (e.g. {{{object template}}} used to define a machine configuration). It is valid for a cluster to have an empty {{{profiles}}} directory. Look at a [source:templates/trunk/clusters/example cluster example].
 
 Other pages describe in more details layout of [wiki:Doc/LCG2/TemplateLayout LCG2 templates] and [wiki:Doc/gLite/TemplateLayout gLite templates].