Changes between Version 31 and Version 32 of Doc/TemplateCustom

Timestamp:

Jul 4, 2007, 11:40:55 AM (17 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…

Comment:

--

Doc/TemplateCustom

@@ -84 +84 @@
 A cluster is associated with one or several sites by the cluster specific file [source:templates/trunk/clusters/example/cluster.build.properties cluster.build.properties]. If associated with several sites, the first one takes precedence over the following one if a template exists in several sites. This ability to associate a cluster with several ''sites'' is a key SCDB feature that can be used for several use cases.
 
+Below is the description for several common use cases. They are presented as distinct use cases for clarity but nothing prevents mixing them.
+
 === Managing several geographical sites from one SCDB ===
 
@@ -92 +94 @@
 In `cluster.build.properties`, you include `mysite` before `gridsite`, with something like :
 {{{
-cluster.pan.includes=mycity mycity/**/* gridsite gridsite/**/*
+cluster.pan.includes=sites/mycity sites/mycity/**/* sites/gridsite sites/gridsite/**/* ...
 }}}
 
@@ -99 +101 @@
 If you want to add a cluster at another geographical location (e.g. `mycity2` belonging to the same grid site, you will just need to adapt this cluster `cluster.build.properties` with something like :
 {{{
-cluster.pan.includes=mycity2 mycity2/**/* gridsite gridsite/**/*
+cluster.pan.includes=sites/mycity2 sites/mycity2/**/* sites/gridsite sites/gridsite/**/* ...
 }}}
 
@@ -106 +108 @@
 In `cluster.build.properties`, you include `mysite` before `gridsite`, with something like :
 {{{
-cluster.pan.includes=mycity mycity/**/*
+cluster.pan.includes=sites/mycity sites/mycity/**/* ...
 }}}
 
+''Note : `sites/` in examples must be replaced by whatever you choosed, if you decided to use another name.''
+
+
 === Supporting production and test clusters ===
+
+This use case is about a site running production systems and test grid systems. They share most of there grid parameters but some of them are differents. This is easily achieved by defining 3 SCDB ''sites'' (in this example, grid site is called `gridsite`) :
+ * `gridsite-prod` : parameters specific to grid production systems
+ * `gridsite-test` : parameters specific to grid test systems
+ * `gridsite` : parameters common to all grid systems at the site
+
+In production cluster `cluster.build.properties`, include path will be defined as :
+{{{
+cluster.pan.includes=sites/gridsite-prod sites/gridsite-prod/**/* sites/gridsite sites/gridsite/**/* ...
+}}}
+
+In test cluster `cluster.build.properties`, include path will be defined as :
+{{{
+cluster.pan.includes=sites/gridsite-test sites/gridsite-test/**/* sites/gridsite sites/gridsite/**/* ...
+}}}
+
+
+''Note : `sites/` in examples must be replaced by whatever you choosed, if you decided to use another name.''
 
 == Hardware Templates ==