Changes between Version 31 and Version 32 of Doc/SCDB/Usage

Timestamp:

Jan 22, 2010, 3:05:53 PM (14 years ago)

Author:

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

Comment:

--

Doc/SCDB/Usage

@@ -172 +172 @@
 === Checking Package Dependencies ===
 
-Profile compilation cannot check if all the dependencies for all packages present in the profile can be satisfied. By default, this is checked by SPMA on the client before trying to deploy de RPM changes. A tool can be used to check dependencies after compilation but before deployment. This is done by analyzing the profile and checking the metadata for each RPM present, using YUM as a source for the dependency metadata. The tool is `utils/checkdeps/checkdeps`. Its usage and requirements are described in a [https://sourceforge.net/apps/mediawiki/quattor/index.php?title=Client_dependencies_check dedicated page].
+Profile compilation cannot check if all the dependencies for all packages present in the profile can be satisfied. By default, this is checked by SPMA on the client before trying to deploy de RPM changes. A tool can be used to check dependencies after compilation but before deployment. This is done by analyzing the profile and checking the metadata for each RPM present, using YUM as a source for the dependency metadata (this requires each RPM repository to be configured as a YUM repository). The tool is `utils/checkdeps/checkdeps`. Its usage and requirements are described in a [https://sourceforge.net/apps/mediawiki/quattor/index.php?title=Client_dependencies_check dedicated page].
 
 One nice feature of `checkdeps` is that it can report missing packages are Pan lines to add to the configuration. This is done with option -p. A typical calling sequence for `checkdeps` is:
@@ -178 +178 @@
 util/checkdeps/checkdeps [-p] -x build/xml/mynode.xml
 }}}
+
+`checkdeps` has a requirement of a recent enough version of YUM. '''This is not possible to run it on a SL4 machine'''. In addition it has a few dependencies that are not installed by default. If you want to be able to run on a Quattor-managed machine, you can add the following to the machine template:
+{{{
+include { 'config/quattor/scdb' };
+}}}
+
+If the machine (must be a Linux one as one requirement is YUM) is not manged by Quattor, read the template for your OS version to know what you need to install.
+
+To configure the RPM repositories as YUM repositories, if the RPM server is managed by Quattor, you can include the following to the machine profile:
+{{{
+# Mandatory: list of directory whose subdirectories may contain RPM. No default.
+# Example: list('/www/htdocs/packages').
+variable QUATTOR_RPM_REPOS_ROOTS ?= list();
+# Optional: path of script to use for creating/updating YUM repositories.
+# variable QUATTOR_YUM_UPDATE_REPOS ?= '/root/quattor/scripts/update_yum_repos';
+# Optional: cron frequency (in hours). Default is 2.
+# variable QUATTOR_YUM_UPDATE_REPOS_INTERVAL ?= 2;
+include { 'quattor/server/yum_repos' };
+}}}
+
+The template `quattor/server/yum_repos` will configure a cron, running every 2 hours by default, to update the YUM repositories. The cron will use a script provided with SCDB, [source:SCDB/trunk/src/misc/update_yum_repos src/misc/update_yum_repos], that you need to copy on the machine running the cron (generally the Quattor server).
 
 === Using panc logging ===