Changes between Version 29 and Version 30 of Doc/SCDB/Usage

Timestamp:

Jan 11, 2010, 9:37:11 AM (14 years ago)

Author:

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

Comment:

--

Doc/SCDB/Usage

@@ -9 +9 @@
 To know how to install a Quattor server with SCDB or how to migrate from CDB, refer to the specific page about [wiki:Download/SCDB SCDB installation].
 
-== Cluster Groups ==
+== Cluster Groups == #ClusterGroups
 
 In SCDB, machine profiles are grouped in ''clusters''. SCDB clusters are arbitrary group of machines and have nothing to do with a batch cluster or an underlying cluster technology. All the nodes in a cluster will share in particular the same ''include path'' for templates (that means that templates will be looked at the same locations for all nodes in the cluster), except for OS templates (see section on [wiki:Doc/OS/Customization#SelectingOSversion selecting OS version] in OS templates documentation).
@@ -125 +125 @@
  * {{{update.rep.templates}}} : this task updates templates describing RPM repositories contents by scanning each repository associated directory.
 
+=== Compiling a selected cluster or cluster group ===
+
+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`:
+ * `cluster.name`: compile profile only in the selected cluster. The value must match the name of an existing cluster. If a cluster with the same name exists in different [#ClusterGroups cluster groups], they will be all compiled except if `cluster.group` is also defined.
+ * `cluster.group`: compile profiles only for clusters belonging to the selected [#ClusterGroups cluster groups]. If `custer.name` is also defined, compile profiles only for this cluster in the selected cluster group.
+
+''Note: To enforce consistency of the whole configuration, SCDB doesn't accept these two options at deployment time. They can be used only during the compilation phase before the deployment.''
+
+After compiling the selected cluster or cluster groups, it is possible to assess the effect of the modification using [#compare_xml utils/profiles/compare_xml] tool.
 
 == Checking Compilation Results and Profile Consistency ==
 
-=== Displaying Resulting Changes in Profile ===
-
-When doing changes in configuration, this is often useful to check the resulting profiles before deploying. There is a small tool to help doing that, [source:SCDB/trunk/src/utils/profiles/compare_xml src/utils/profiles/compare_xml]. This tool is part of [source:SCDB/trunk SCDB base].
+=== Displaying Resulting Changes in Profile === #compare_xml
+
+When doing changes in configuration, this is often useful to check the resulting profiles before deploying. There is a small tool to help doing that, [source:SCDB/trunk/utils/profiles/compare_xml utils/profiles/compare_xml]. This tool is part of [source:SCDB/trunk SCDB base].
 
 To use this tool, before compiling your changes, you need to copy your current (or reference) `build` directory to something else, by example `build.saved` (default name used by the script). After the compilation, if you run the script without arguments, it will display the list of all profiles that have changed. You can inspect the changes (require a bit of knowledge of profile contents) using option `-v`. Or you can restrict the check to one specific profile with option `-p`. By example :
 
 {{{
-# src/utils/profiles/compare_xml
+# utils/profiles/compare_xml
 
 Comparing XML files (*.xml)...
@@ -142 +151 @@
 Differences found in build/xml/profile_grid07.xml
 
-# src/utils/profiles/compare_xml -v -p profile_grid05
+# utils/profiles/compare_xml -v -p profile_grid05
 
 Comparing XML files (profile_grid05.xml)...