Changes between Version 80 and Version 81 of Download/SCDB

Timestamp:

Mar 11, 2009, 7:48:48 PM (17 years ago)

Author:

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

Comment:

--

Download/SCDB

@@ -315 +315 @@
    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 QWG templates gLite-3.0.2-10 do:
-{{{
-check-compile.sh -d cdb /templates/tags/gLite-3.0.2-10
+   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: 
@@ -363 +363 @@
 want to customize it later, you are probably better to start with a
 configuration similar to what is provided in `repository` directory of
-`sites/example` directory. You can retrieve an initial directory
-content for each RPM repository by downloading the contents of the URL
-specified in comments at the beginning of each repository templates.
+`sites/example` directory. 
+
+You can retrieve an initial directory content for each RPM repository by downloading the contents of the URL
+specified in comments at the beginning of each repository templates. A convenient way to do it is:
+{{{
+src/utils/misc/rpmUpdates /your/dir/ectory URL_found_in_template_header > /dev/null
+}}}
+
+''Note: this command produce a rather verbose output, just ignore it.''
+
+You have to do it for the following repository templates:
+ * OS: to start, you need only to download the OS version you plan to use. ''Note: there are several repositories per OS versions, be sure to download all of them.''
+ * gLite: to start download all the repositories related to the version you are planning to use, ignore others.
+ * All the repositories not related to an OS or gLite version
+
+You are probably better to remove any template you think you will not use (you can always revert your change in case of mistakes).
 
 === Basic System Configuration ===
 
 Basic system configuration (network parameters, DNS servers, ...) are
-grouped in template `pro_site_cluster_info.tpl` in `site` directory of
+grouped in template `pro_site_config.tpl` and `pro_site_global_variables.tpl`  in `site` directory of
 your site. Look at comments to understand what you need to modify.
 
@@ -379 +392 @@
 comments to understand what you need to modify.
 
+''Note: do not be afraid of putting wrong values in your gLite parameters, this can easily be refined later. As a general rule, keep the example values when you don't understand how to change them.''
+
 
 == Cluster Configuration ==
 
 After creating your site, you need to create your first cluster. You
-can do this by copying `clusters/example` directory and customizing a
+can do this by copying `clusters/example-3.1` directory, removing all profiles from `clusters/example-3.1/profiles` and customizing a
 few templates.
 
@@ -389 +404 @@
 
 You need to create a template describing the hardware configuration of
-your machines. This is generally placed in `hardware`sub-directory of
-site directory. Look at examples.
+your machines. This is generally placed in `hardware` sub-directory of
+site directory. Look at examples, copy one with a configuration close to yours as a starting point. The name of the hardware template is at your convenience and will be associated with a host name later.
+
+''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 ===
 
 Before being able to configure the machine, you need to create an
-entry for the machine name in both tables of
-`pro_site_database.tpl`. First entry defines the address associated
-with the machine name, second entry defines the hardware template
-associated with the machne.
+entry for the machine name in both variables of
+`pro_site_database.tpl`. First variable defines the address associated
+with the machine name, second variable defines the hardware template
+associated with the machine.
+
+In both variable, the key is the escaped host name. The value is an IP address in the first case, the name of the template (relative to your site name in `sites` directory) you created in the previous step for the second variable.
 
 === Creating Machine Profile ===
@@ -404 +423 @@
 Copy an existing profile in examples corresponding to the machine type
 you want to create.
+
+''Note: as a first node, it is recommended to configure a site BDII as this is the most simple node. When successful with site BDII, the next ones are generally CE and one WN.''
 
 == Quattor Server Final configuration ==