Generating Templates for OS and gLite

TOC(inline)

OS Templates

OS Templates describing RPM list for each OS feature goup are entirely generated from standard Red Hat (or SL) provided comps.xml file. This is a 3 steps process :

• rpmProvides.pl: generate a file describing features provided by each RPM in OS distribution
• rpmRequires.pl : generate a file describing for each RPM in the distribution the required dependencies. Uses file produced by previous step as input.
• comps2pan.xsl : generate the templates from standard comps.xml file provided in OS distribution. Uses file produced by previous step as input.

It is important to use the namespace parameter in comps2pan.xsl and indicates rpmlist as value.

All these tools are in utils/misc in Quattor CVS.

gLite Templates

Templates for pure gLite services are generated from file .conf.xml provided in the config RPM associated with each service. This is done by create_template.pl tool, utils/misc in Quattor CVS. This tool generates 3 templates per service :

• config.tpl : the entry point
• schema.tpl : defines all the supported PAN resources/properties for this component
• defaults.tpl : defines a sensible default value for each property, according to the content of XML file for the service.

All these templates used namespaces and their layout is service oriented. There is one directory per service, containing all the templates for the service. All these directories must be placed in common/glite directory of gLite templates.

Trusted CAs Template

Trusted CAs are described in a set of RPMs, update regularly. There is one template describing all the trusted CAs RPMs that must be loaded. This is :

• For gLite : common/security/cas.tpl
• For LCG 2.7 : rpmlist/pro_software_lcg2_service_security_accepted_cas.tpl

This template is generated from the contents of the RPM repository containing CAs RPMS with the tools create_template.tpl