Changes between Version 88 and Version 89 of Download/SCDB

Timestamp:

Nov 7, 2009, 6:18:31 PM (16 years ago)

Author:

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

Comment:

--

Download/SCDB

@@ -190 +190 @@
  * `branches` : for alternative developments
 
-For example:
-
-{{{
-mkdir toto
-cd toto
-mkdir scdb
-mkdir scdb/trunk
-mkdir scdb/tags
-mkdir scdb/branches
-svn import scdb https://svn.server.tld/svn/quattor --message 'Initial repository layout'
+One of the possible methods to create it with an empty Quattor repository (or repository branch) is (assuming your repository is dedicated to SCDB and its URL is http://svn.example.org/Quattor):
+
+{{{
+mkdir /tmp/scdb
+cd /tmp/scdb
+mkdir trunk
+mkdir tags
+mkdir branches
+svn import . http://svn.example.org/Quattor --message 'Initial repository layout'
 }}}
 
@@ -298 +297 @@
 product. The http based repository access '''must''' be used for
 quattor, the standalone access won't work (limitation of the build
-script).
-
-After you have a Subversion server installed, you need to :
-
- * Create a Subversion repository that will be used for SCDB (if it
-   doesn't already exist) and associate this repository with a URL (this
-   can involve modifying Apache configuration). There is no need to
-   use a dedicated repository. For example:
-   `http://svn.example.org/Quattor`.
- * If the repository is not dedicated to SCDB, create a branch in this repository where SCDB will be stored,
-    For example:
-   `http://svn.example.org/Quattor/CDB`.
- * In this branch, create 2 branches `trunk` and `tags` (`tags` is
-   managed by SCDB tools, all the actions you'll do later will be done
-   in `trunk`. You can also create other branches for your
-   conveniences (like `branches` but they are not used by standard
-   tools).
- * Populate your repository with the version of SCDB and QWG templates
-   you want to use.  The easiest is to download
-   and use [source:templates/trunk/tools/check-compile.sh?format=txt check-compile.sh]
-   (use option `-h` to get the list of available
-   options).  This will download SCDB, QWG, and compile the example to 
-   ensure that everything works.  To populate the `cdb` subdirectory for example,
-   with SCDB and last version from gLite 3.1 branch do:
-{{{
-check-compile.sh -d cdb glite-3.1
-}}}
-   The equivalent can be done manually.  See the following link for SCDB and QWG: 
-   [source:SCDB/tags/pro SCDB base] and [wiki:Download/QWGTemplates QWG download]. 
+script). 
+
+You must have created a repository for Quattor and initialized its structure as explained in section [].
+
+To create your initial SCDB with the standard templates and the associated examples, follow the following steps:
+ * Populate your repository with the version of SCDB and QWG templates you want to use.  The easiest is to download and use [source:templates/trunk/tools/check-compile.sh?format=txt check-compile.sh] (use option `-h` to get the list of available options).  This will download SCDB, QWG, and compile the example to  ensure that everything works.  To populate the `cdb` subdirectory for example, with SCDB and last version from gLite 3.1 branch do:
+{{{
+check-compile.sh -d scdb glite-3.1
+}}}
  * Change current directory to the working area, for example :
 {{{
-cd cdb
+cd scdb
 }}}
  * Checkout SCDB trunk (empty) in your SCDB working directory :
@@ -423 +402 @@
 ''Note: recommendation is to have name of templates describing HW boxes derived from box location rather than its current host name as the same HW may be affected to another host later.''
 
-=== Adding Machine to pro_site_database.tpl ===
+=== Adding Machine to site/database.tpl ===
 
 Before being able to configure the machine, you need to create an
 entry for the machine name in both variables of
-`pro_site_database.tpl`. First variable defines the address associated
+[source:QWG/trunk/sites/example/site/databases.tpl databases.tpl]. First variable defines the address associated
 with the machine name, second variable defines the hardware template
 associated with the machine.