Changes between Version 23 and Version 24 of Doc/TemplateCustom
- Timestamp:
- Jun 27, 2007, 8:19:42 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/TemplateCustom
v23 v24 20 20 The suggested layout is : 21 21 22 * [source:templates/trunk/ grid/os os] : this hierarchy is used for OS related templates (e.g. RPMs associated with each feature group). Generally this hierarchy is made of one sub-hierarchy per OS version/architecture (e.g. [source:templates/trunk/os/sl308-i386 sl308-386], [source:templates/trunk/os/sl440-x86_64 sl440-x86_64]). Most of the templates in these hierarchy are generated from OS distribution and should not be edited.23 * [source:templates/trunk/grid /gridgrid] : 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.22 * [source:templates/trunk/os os] : this hierarchy is used for OS related templates (e.g. RPMs associated with each feature group). Generally this hierarchy is made of one sub-hierarchy per OS version/architecture (e.g. [source:templates/trunk/os/sl308-i386 sl308-386], [source:templates/trunk/os/sl440-x86_64 sl440-x86_64]). Most of the templates in these hierarchy are generated from OS distribution and should not be edited. 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. 24 24 * [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. 25 25 * [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]. … … 30 30 == Clusters and Template Hierarchies == 31 31 32 Each cluster is can be associated with one middleware version or sites by defining the appropriate include path used by pan compiler to locate templates. This include path is defined in the file [source:templates/trunk/clusters/example/clluster.build.properties cluster.build.properties] at the top of each cluster hierarchy, (`cfg/clusters/`''cluster-name'').32 Each cluster is associated with one middleware version or sites by defining the appropriate include path used by pan compiler to locate templates. This include path is defined in the file [source:templates/trunk/clusters/example/cluster.build.properties cluster.build.properties] at the top of each cluster hierarchy, (`cfg/clusters/`''cluster-name''). 33 33 34 34 This file must contain one line defining the property {{{cluster.pan.includes}}} as a list of space separated hierarchy list. The hierarchy is interpreted as a file pattern relative to the {{{cfg}}} directory (or whatever has been specified for {{{cfg}}} property in file [source:SCDB/trunk/quattor.build.xml quattor.build.xml]). It must specify a directory that the template name (including it's relative position in the directory) must be appended to to locate the template file. … … 38 38 ''Note : Legacy template names, as defined in the `template` statement at the beginning of the template, don't include the relative position of the template in its template hierarchy (called ''namespace''). To include seach templates if they are spread to several sub-directories of the template hierarchy, you can specify to use all subdirectories instead of listing them explicitly, appending the pattern `/**/*` at the trail of the directory name. This entry must be added '''after''' the normal entry. With such legacy templates, if a template exists in several directories of a hierarchy, the inclusion order is unspecified.'' 39 39 40 Look at [source:templates/trunk/cluster /examples/cluster.build.properties cluster.build.properties] example. As reflected by this example, hierarchies of standard templates '''must''' be included after site specific templates (there may be several sites the cluster belongs to), in the following order : `grid`, `os` and `standard`.40 Look at [source:templates/trunk/clusters/example/cluster.build.properties cluster.build.properties] example. As reflected by this example, hierarchies of standard templates '''must''' be included after site specific templates (there may be several sites the cluster belongs to), in the following order : `grid`, `os` and `standard`. 41 41 42 42 ''Note : `clusters/cluster-name` hierarchy is implicitly added as the first entry in the include path. It should not be added explicitly to the `cluster.build.properties` file.''
