Changes between Version 35 and Version 36 of Doc/SCDB/Usage
- Timestamp:
- Jun 24, 2011, 3:00:40 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/SCDB/Usage
v35 v36 44 44 }}} 45 45 46 === Cluster Group Parameters === 46 === Cluster Group Parameters === #ClusterGroupParams 47 47 48 48 In addition to specifying cluster parameters, like PAN include path, into the cluster specific file [source:QWG/templates/trunk/clusters/example-3.2/cluster.build.properties cluster.build.properties], it is possible to define parameters common to all clusters in the cluster group in the file `cluster.group.build.properties` (in the group root directory). The same parameters can be defined in both configuration files: parameters defined in the cluster-specific file takes precedence. … … 54 54 Instructions below are a ''survival kit'' for new Subversion users. There is in fact nothing SCDB specific. The examples are provided using the SVN command line interface. For more detailed information, refer to [http://svnbook.org/ Subversion documentation]. But all these operations can be done with any SVN client : they are many GUIs available that can ease the interaction with Subversion. One very interesting and featureful GUI is [wiki:Doc/SCDB/Eclipse Eclipse] that integrates very well with SCDB. 55 55 56 === Creating a SCDB Working Copy === 56 === Creating a SCDB Working Copy === #SCDBWC 57 57 58 58 This is the first thing to do. Generally this is done in a permanent area, to avoid redoing it every time you need to do a modification. The SVN operation to do this is called ''checkout'' and can be done with the following command line : … … 63 63 This example assumes that the URL of template branch in SCDB repository is `http://mysvn.server.example.com/SCDB/trunk`. 64 64 65 === Getting Status of Working Copy === 65 === Getting Status of Working Copy === #SCDBWCStatus 66 66 67 67 You can get list of all the modified files in your working copy with command `svn status`. By default this command checks status of files against the base revision of the working copy but doesn't check against the repository. Thus it can be used even if you are disconnected from the network. If you want to check the status of files in the working copy against the repository, you need to add option `-u`. … … 95 95 }}} 96 96 97 === Revert Changes === 97 === Revert Changes === #SCDBRevert 98 98 99 99 With Subversion it is very easy to revert changes, whether they have been commited or not. But the procedure is not exactly the same. … … 119 119 There are in fact many possible variations in `svn merge` command. You can choose to revert a change between 2 arbitrary revisions and not only between the last one and a ''good one''. Also you can roll back the changes for only some directories or files. In this case you have to give 2 additional parameters : first one is the repository branch containing the directory/files, second one is the directory/file in the working copy the changes must be merged into. 120 120 121 == Template Compilation == 121 == Template Compilation == #TemplateCompilation 122 122 123 123 All the template processing needed to build machine profiles is done with {{{ant}}} tools, a Java based equivalent of {{{make}}}. {{{ant}}} brings the advantage of platform independance, allowing to do Quattor management tasks on any platform (Unix, Windows, MacOS). … … 129 129 * {{{update.rep.templates}}} : this task updates templates describing RPM repositories contents by scanning each repository associated directory. 130 130 131 === Compiling a selected cluster or cluster group === 131 === Compiling a selected cluster or cluster group === #ClusterGroupCompile 132 132 133 133 When doing modification to templates in a configuration with a large number of nodes, it is often desirable to be able to assess the modification on a small number of nodes, as compiling all node profiles generally result in a long turnaround. SCDB offers several options to do this, passed to `ant` with option `-Doption=value`: … … 174 174 Another option available, `-d`, extends the comparaison to profile dependencies. This is generally not useful but can be used to do a regression test with a new version of the compiler, for example. 175 175 176 === Checking Package Dependencies === 176 === Checking Package Dependencies === #checkdeps 177 177 178 178 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 [wiki:Web/CheckDeps#Runningcheckdeps Quattor Tool Catalog]. … … 204 204 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). 205 205 206 === Using panc logging === 206 === Using panc logging === #panclogging 207 207 208 208 Version 8 of the Pan compiler introduces some useful logging facilities that are helpful for debugging (for example, the order of template inclusion and function calls can be logged). These features can be used from SCDB by setting options as follows: … … 218 218 }}} 219 219 220 === Using panc debugging === 220 === Using panc debugging === #pancdebug 221 221 222 222 Version 8.2.4+ of the Pan compiler allows selective output of debugging statements. You can use debug statements freely in templates, and then select when running the compiler which templates should output the debug information. This is done by specifying a set of include and exclude patterns that select sets of templates. You can use this from SCDB via options to ant as follows:
