| 16 | | * {{{machine-types}}} : |
| 17 | | * {{{rpmlist_sl3}}} : |
| 18 | | * {{{sources}}} : |
| 19 | | * {{{vo}}} : |
| 20 | | * {{{vo2}}} : |
| | 16 | * {{{machine-types}}} : templates defining the whole configuration of a given LCG2 machine type (e.g. WN, CE, SE, BDII...). There is one template per machine type. They all rely on template {{{pro_lcg2_machine_config_base}}} to define basic configuration of any kind of LCG2 machine. |
| | 17 | * {{{rpmlist}}} : templates defining RPMs that must be loaded for a given LCG2 service. These RPMs are generated from LCG2 middleware description and '''should not''' be edited manually (manual edits will be lost next time templates are generated). |
| | 18 | * {{{repository}}} : there is normally one template listing all the RPM repositories associated with the current version of the middleware. Each repository is defined in a template that is site specific. |
| | 19 | * {{{sources}}} : templates that define a LCG2 service configuration. These templates are maintained manually and generally need to be updated with each version of the middleware. They are centrally maintained by QWG maintainers. These templates are generic and take as input variables to define a specific site configuration. They '''should not'' (normally) be edited manually. |
| | 20 | * {{{vo-legacy}}} : templates to define VOs, using scheme used by previous version of QWG templates (until 2.7.0). They are provided for backward compatibility but should not be used anymore, after migrating to the new, much more flexible, scheme. |
| | 21 | * {{{vo}}} : templates to configure VOs. These templates and associated functions provide a flexible way of configuring VOs. They take as input the list of VOs to be configured, from variable VOS. |
