| Version 2 (modified by , 18 years ago) (diff) |
|---|
QWG Templates and Site Customization
Table of Contents
This page describes the template framework structure QWG templates is part of and how to integrate site custimizations into this framework.
QWG template framework has been designed to achieve the following goals :
- Provide generic templates for software installation and configuration, with local site parameters separated from provided templates.
- Preserve site customization across software upgrades (OS or middleware)
- Allow support of several sites sharing some configuration database, leveraging overall management load but keeping required flexibility.
Template Hierarchies
QWG LCG2 templates rely on a basic template structure based on template hierarchies. Each template hierarchy is dedicated to one specific aspect of the configuration, e.g. OS, LCG middleware, site specific parameters...
There is no imposed naming of template hierarchies, except for the clusters hierarchy which must contain cluster definition. clusters is the only hierarchy searched for machine profiles.
The suggested layout is :
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. sl305-i386, sl305-x64). Most of the templates in these hierarchy are generated from OS distribution and should not be edited.egee: 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. lcg-2.7.0, glite-1.5.0). This hierarchy typically contains templates provided by QWG LCG. Most of these templates are configurable through variable definition and should require no edit.standard: this hierarchy is used for other kind of standard templates provided by some products, e.g. Quattor core templates, pan standard templates, Lemon templates... Generally this hierarchy contains one directory tree for each product. The templates in this hierarchy should not be edited.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.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 directoryprofilescontaining the machine profiles (e.g.object templateused to define a machine configuration). It is valid for a cluster to have an emptyprofilesdirectory.
Other pages describe in more details layout of LCG2 templates? and gLite templates?.
