Changes between Version 21 and Version 22 of Doc/SCDB/Usage


Ignore:
Timestamp:
Aug 17, 2009, 10:52:55 PM (15 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/SCDB/Usage

    v21 v22  
    1414
    1515Since 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
     17To 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:
     18{{{
     19# Enable cluster groups (default is false for backward compatibility)
     20clusters.groups.enable=true
     21
     22# Enable creation of directory per group in build/xml.
     23# Default should be appropriate for standard deployment model.
     24clusters.groups.xml=false
     25
     26# Generate profiles-info.xml as part of cluster group compilation
     27# Default should be appropriate for standard deployment model.
     28clusters.groups.build.info=false
     29
     30# Define root directory (under cfg/ for all cluster groups or clusters)
     31clusters.directory=clusters
     32}}}
     33
     34Each 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.
     35
     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:''
     37{{{
     38svn propedit [--editro-cmd vi] svn:ignore .
     39}}}
    1640
    1741