Changes between Version 13 and Version 14 of Doc/TemplateCustom
- Timestamp:
- Dec 7, 2006, 7:55:24 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/TemplateCustom
v13 v14 109 109 Configuration common between several clusters is stored in a site hierarchy, stored under {{{sites}}} directory. As far as Quattor is concerned, a ''site'' doesn't have to match a geographical location but is an abstract entity corresponding to a set of shared configuration parameters. Very often, a cluster will belong to several ''sites'' corresponding to different set of common parameters. For example, in the above example, the cluster belongs to 2 sites : {{{lal}}} and {{{grif}}}. {{{lal}}} defines parameters corresponding to a specific geographical locations (like network related parameters) that are common to all kind of clusters (grid machines, non grid servers, desktops...). {{{grif}}}, on the other hand, defines parameters that are common to all grid machines, whatever geographical location they belong to. 110 110 111 == Hardware Templates == 112 113 Hardware configuration of machines is described as part of the machine profiles through a set of templates. There is one template for each kind of hardware subsystem (CPU, memory, nic...). They are located in [source:templates/trunk/standard/hardware standard/hardware]. There is one subdirectory for each kind of hardware subsystem. There is also a `legacy` subdirectory with templates in the old format (non namespaced). 114 115 The recommandation is to create one template per machine that includes the appropriate templates to describe the machine hardware. The suggested location for these site specific templates are in `hardware/machine` in site directory. Look at [source:templates/trunk/site/example/hardware] examples for more information. 116 111 117 == Template Compilation Tool == 112 118 113 The recommended method to process all the templates and build machine profiles is to use {{{ant}}} tool, a Java based equivalent of {{{make}}}, provided with SCDB (it can also be used without SCDB). {{{ant}}} brings the advantage of platform independance, allowing to do Quattor management tasks on any platform (Unix, Windows, MacOS).119 The recommended method to process all the templates and build machine profiles is to use {{{ant}}} tool, a Java based equivalent of {{{make}}}, provided with SCDB (it can also be used without SCDB). {{{ant}}} brings the advantage of platform independance, allowing to do Quattor management tasks on any platform (Unix, Windows, MacOS). 114 120 115 121 Look at [wiki:Doc/SCDB/Usage SCDB usage] documentation for more information on how to use this tool.
