Changes between Version 3 and Version 4 of Obsolete/Development/Templates/gLite

Timestamp:

Jul 25, 2008, 10:23:57 AM (17 years ago)

Author:

jouvin

Comment:

--

Obsolete/Development/Templates/gLite

@@ -17 +17 @@
 In addition to templates describing services, there is generally one template called a ''machine type'' template, sitting in `machine-types` directories of grid templates. This template does everything required to configure a machine with the corresponding high-level services, including OS configuration. When a high-level service has several configuraion variants (e.g. WMS and/or LB, DPM head node or disk servers), there is generally only one machine-type template with a variable allowing to select the appropriate variant for one specific machine.
 
-
-
+Each service description is arranged basically around the same layout, with generally at least 3 templates for high-level services:
+ * `config.tpl`: this templates does all the configuration specific to the service, whether high-level or low-level but doesn't take care of loading packages used by the service and is not responsible for configuring other services used by the service. In some services, the name of the template may be different, if more appropriate.
+ * `service.tpl`: this template configures every low-level service used by the high-level service, including the specific configuration (`config.tpl`) and RPMs (`rpms/config.tpl) for the service. This template exists only for high-level services and is the main ''entry point'' for configuring the service.
+ * `rpms/config.tpl` : this template is responsible for adding all the packages (RPMs) used by the service. It seldom exists in low-level services but is always present in high-level service. Generally this template mainly includes another template which does the real work and is architecture specific. The architecture specific templates must be in a directory  `rpms/arch` (e.g. `rpms/x86_64`) and is generally called `config.tpl` but may have another name if more appropriate, in particular in services supporting several variants (like DPM, dCache...).
  
 
@@ -32 +34 @@
 
 === RPMs ===
+
+For each gLite service in [source:templates/trunk/grid/glite-3.1/glite glite/] directory, there is a list of the required RPMs for the service. This list is mainly generated from official list supplied by [http://glite.org gLite] with the release. It generally requires some manual tuning to solve some missing dependencies in the list provided by gLite. After the initial release, this list should not be edited, except for adding a new RPM required by an update. Replaced RPMs must be handled by [wiki:Development/Templates/Generated#ListofupdateRPMs update related] templates.
+
+To generate the template from the gLite supplied list, you need to use [source:SCDB/trunk/src/utils/misc/createPackagesTemplate src/utils/misc/createPackagesTemplate] script provided with SCDB. The steps are :
+ * Download the official list from [http://glite.org gLite] site. For example for gLite 3.1 WN, download http://glite.web.cern.ch/glite/packages/R3.1/deployment/glite-WN/3.1.0-1/glite-WN-3.1.0-1.html.
+ * Process this file with [source:SCDB/trunk/src/utils/misc/createPackagesTemplate src/utils/misc/createPackagesTemplate] script :
+{{{
+src/utils/misc/createPackagesTemplate --rpmlist glite-WN-3.1.0-1.html \
+                                      --template cfg/grid-3.1/glite/wn/rpms/i386/rpms.tpl \
+                                      --namespace glite/wn/rpms/i386
+}}}
+
+
 
 === service.tpl ===