| 45 | | === Templates for services managed by ncm-glite === |
| 46 | | |
| 47 | | Some of the gLite services are managed with a generic component, `ncm-glite`. For each service managed by this component, there is a directory in [source:templates/trunk/grid/glite-3.1/components/glite components/glite] directory defining the supported configuration options for this service. |
| 48 | | |
| 49 | | These per service templates are generated from file `.conf.xml` provided in the config RPM associated with each service. This is done by a set of tools in `utils` directory of `ncm-glite` component sources, in [http://quattor.org/software.htm Quattor CVS]. This tool generates 3 templates per service : |
| 50 | | * `config.tpl` : the entry point |
| 51 | | * `schema.tpl` : defines all the supported PAN resources/properties for this component |
| 52 | | * `defaults.tpl` : defines a sensible default value for each property, according to the content of XML file for the service. |
| 53 | | |
| 54 | | Look at `README` file in `utils` directory for instructions on how to use the tools and generate these files. |
| 55 | | |
| 56 | | Before using this tool, all the glite*-config*rpm must be installed on the machine where the tool will be run. |
| 57 | | |
| 58 | | |
| 63 | | Generally all update RPMs for one product version are kept in one directory. There is a tool to help producing the associated template with the last version of each RPM in this directory, [source:SCDB/trunk/src/utils/misc/rpmUpdates.pl src/utils/misc/rpmUpdates.pl/rpmUpdates.pl], which is part of the [source:SCDB SCDB base]. This script accept one argument, the RPM repository directory, and write the template on `stdout` which must be redirected to a file. |
| | 49 | Generally all update RPMs for one product version are kept in one directory. There is a tool to help producing the associated template with the last version of each RPM in this directory, [source:SCDB/trunk/src/utils/misc/rpmUpdates.pl src/utils/misc/rpmUpdates.pl/rpmUpdates.pl], which is part of the [source:SCDB SCDB base]. This script accept one argument, the RPM repository directory, and write the template to `stdout` which must be redirected to a file. |
| | 50 | |
| | 51 | === gLite Update Specifities === |
| | 52 | |
| | 53 | gLite updates are periodically released and are designated by a number. QWG templates provide the templates required to configure a specific update in a directory `update/nn` in gLite templates, where `nn` is the official gLite update number. This directory contains 2 or more templates : |
| | 54 | |
| | 55 | * `config.tpl` : this is the main template used to include other templates required by the update. It generally mainly includes `rpms.tpl`. |
| | 56 | * `rpms.tpl` : list of RPMs updated by the gLite update. This is normally the output of [source:SCDB/trunk/src/utils/misc/rpmUpdates.pl src/utils/misc/rpmUpdates.pl/rpmUpdates.pl] '''unedited'''. |
| | 57 | * `init.tpl` (optional) : a template defining some specific configuration options at the very beginning of the node configuration. This can be used to define variables used by other standard templates, e.g. `CONDOR_VERSION`. |
| | 58 | * update post-config per machine type (optional) : such templates define actions specific to a node type, as installing a specific version of a RPM. This is done after the standard update configuration (`config.tpl`). To be used the template name must be the value of variable `GLITE_UPDATE_POSTCONFIG` (generally defined in a machine type template). |
