Changes between Version 145 and Version 146 of Doc/gLite/TemplateCustomization

Timestamp:

Jan 7, 2010, 11:17:04 AM (16 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Doc/gLite/TemplateCustomization

@@ -930 +930 @@
 
 In addition to the previous variable, it is possible to use variable `GRID_TRUSTED_BROKERS` to define the WMS which are allowed to use the MyProxy server. The list provided with this variable is merged with `MYPROXY_AUTHORIZED_RENEWERS`.
+
+== VOMS Server ==
+
+__Base template__ : `machine-types/voms`.
+
+VOMS server default configuration can be customized with the following variables:
+ * `VOMS_VOS`: this variable describe each VO managed by the VOMS server. This is a nlist where the key is the VO name and the value a nlist specifiying the VO parameters. A typical entry is:
+{{{
+  'vo.lal.in2p3.fr',  nlist('port', '20000',
+                            'host', 'grid12.lal.in2p3.fr',
+                            'dbName', 'voms_lal',
+                            'dbUser', 'root',
+                            'dbPassword', 'clrtxtpwd',
+                            'adminEmail', 'vomsadmins@example.com',
+                            'adminCert', '/etc/grid-security/vomsadmin.pem',
+                           ),
+}}}
+ * `VOMS_DB_TYPE`: can be `mysql` or `oracle`.
+ * `VOMS_MYSQL_ADMINPWD`: password of the MySQL administrator account (MySQL account). Required if DB type is `mysql` (no default).
+ * `VOMS_MYSQL_ADMINUSER`: username of the MySQL administrator account (MySQL account). Ignored if DB type is not `mysql`. Default: `root`.
+ * `VOMS_ADMIN_SMTP_HOST`: STMP host used by VOMS admin when sending emails. Default: `localhost`.
+ * `VOMS_CRON_EMAIL`: user to notify in case of problems during cron jobs. Default: `root@localhost`.
+
+In addition to configuring the previous variable, it is generally necessary to install the certificate of the initial administrator of the VO. This certificate is passed in paramater `adminCert` in VO parameters (`VOMS_VOS`). This is typically done with Quattor configuration module `filecopy` in the site-specific configuration of the VOMS server. A typical sequence to do this is:
+{{{
+include { 'components/filecopy/config' };
+variable CONTENTS = <<EOF;
+-----BEGIN CERTIFICATE-----
+... Copy certificate from the PEM file ...
+-----END CERTIFICATE-----
+EOF
+
+# Now actually add the file to the configuration.
+'/software/components/filecopy/services' = 
+  npush(escape('/etc/grid-security/vomsadmin.pem'), 
+        nlist('config',CONTENTS,
+              'perms','0755'));
+}}}
+
 == VOBOX ==