Changes between Version 25 and Version 26 of Doc/SCDB/Usage
- Timestamp:
- Aug 18, 2009, 8:30:09 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/SCDB/Usage
v25 v26 15 15 Since SCDB [milestone:SCDB-2.3.1 2.3.1], it is possible to define cluster groups. Previously all clusters where corresponding to one directory under `clusters` directory. It is now possible to group them into several cluster groups matching your site organization (groups can match a geographical location, an organisational group... SCDB makes no assumption about this). Every group will correspond to one directory in `clusters` directory and every cluster will have one directory in the group it belongs to. 16 16 17 To activate cluster groups, you need to create a file `quattor.build.properties` in the root directory of your SCDB installation (the same directory where `quattor.build.xml` resides). In this file, you can define the following properties:17 To activate cluster groups, you need to create a file `quattor.build.properties` (see [#ConfiguringSCDBAntTools documentation] for the syntax description of this file) in the root directory of your SCDB installation (the same directory where `quattor.build.xml` resides). In this file, you can define the following properties: 18 18 {{{ 19 19 # Enable cluster groups (default is false for backward compatibility) … … 32 32 }}} 33 33 34 Each of the properties above is optional, values showed in the example above are the default ones, except for `clusters.groups.enable`. `#` is the comment sign. Be aware that everything after `=` is considered part of the value and that there should be no quote or double quotes around values or they will be considered part of the value.34 Each of the properties above is optional, values showed in the example above are the default ones, except for `clusters.groups.enable`. 35 35 36 36 ''Note: you need to check SVN property `svn:ignore` on SCDB root directory to ensure `quattor.build.properties` is not ignored as it used to be recommended to put it in the svn:ignore list. To check, use the following command:''