Changes between Version 83 and Version 84 of WRF4GTutorial2

Timestamp:

Mar 31, 2013 2:55:28 PM (9 years ago)

Author:

carlos

Comment:

--

WRF4GTutorial2

@@ -179 +179 @@
 * FORK
 * !LoadLeveler
-* MN SLURM (only for Red Española de Supercomputación)
+* SLURM
  
-In order to add new resources, you need to edit `Computing Resources` section in the [wiki:WRF4Gframework4g_conf framework4g.conf] file which is located under `$WRF4G_LOCATION/etc` directory. The file has to contain one resource per line with the format:
-
-{{{
-   resource_name   attributes
+In order to add new resources, you need to edit `ComputingResources` section in the [wiki:WRF4Gframework4g_conf framework4g.conf] file which is located under `$WRF4G_LOCATION/etc` directory. The file has to contain one resource per line with the format:
+
+{{{
+   resource_name  = attributes
    ...     ...
-   resource_name   attributes
+   resource_name  = attributes
 }}}
 
 where:
-* '''resource_name''': is the name of the resource.
-* '''attributes''': are the static attributes of the resource and their syntax is:
- * `<scheme>://<username>@<host>?<query>`
-  * '''scheme''': the URL schemes available are "ssh" and "local".
-    * '''ssh''':   access to remote DRM via SSH
-    * '''local''': use the local DRM 
-  * '''username''': user name 
+* '''resource_name''': It is the name of the computing resource.
+* '''attributes''': They are the static attributes of the computing resource. The syntax is:
+ * `<scheme>://<username>@<host:port>?<query>`
+  * '''scheme''':  URL schemes available are "ssh" and "local".
+    * '''ssh''':   In order to connect to remote resource via SSH
+    * '''local''': In order to use a local resource
+  * '''username''': user name on the resource
   * '''host''': host name
-  * '''query''': contains additional information. The query string syntax is:
+  * '''port''': host port to connect to. By DEFAULT is 2
+  * '''query''': contains additional information of computing resources. The query string syntax is:
     * key1=value1;key2=value2;key3=value3
 
 The keys available are:
-* '''LRMS_TYPE'''(mandatory): DRM system for execution [pbs | sge | fork | loadleveler | mnslurm ] 
-* '''PROJECT'''(optional for SGE, PBS and !LoadLeveler): specifies the user's project on the computing resource
-* '''GW_RUNDIR'''(optional): directory on the computing resource in which simulation jobs are deployed. By default, it is user's home. '''Be carefully with this variable''', we recommend you change this directory in production because the home directory usually has a low quote (have to be an absolute path)   
-* '''GW_LOCALDIR'''(optional): defines the working directory on the computing resource (have to be an absolute path)
-* '''NODECOUNT'''(optional): total number of slots on the DRM system (cores)  
-* '''QUEUE_NAME'''(optional): the name of the queue to configure  
+* '''LRMS_TYPE'''(mandatory): Type of LRMS system [pbs | sge | fork | slurm ]
+* '''NODECOUNT'''(mandatory): Maximum number of job slots for a resource.
+* '''QUEUE_NAME'''(mandatory): Queue name to configure. It is mandatory except for "LRMS_TYPE=fork"
+* '''SSH_KEY_FILE'''(optional): It defines the key file for "ssh" connection. By DEFAULT is ~/.ssh/id_rsa.
+* '''PROJECT'''(optional): It specifies the project which the jobs are assigned. It is only optional for SGE and PBS.
+* '''PARALLEL_TAG'''(optional): It defines the parallel environments available for SGE.
+* '''TEMP_DIR'''(optional): Temporary directory used by DRM4G on the resource to temporarily store data. By DEFAULT is $HOME. TEMP_DIR path must be absolute.
+* '''RUN_DIR'''(optional): Temporary directory used to run WRF Model on the resource. By DEFAULT is $HOME. RUN_DIR path must be absolute.
 
 Examples of configuration:
 {{{
-mycomputer    local://localhost?LRMS_TYPE=fork;NODECOUNT=2
-}}}
-{{{
-PBS_cluster   local://localhost?LRMS_TYPE=pbs;QUEUE_NAME=estadistica
-}}}
-{{{
-SGE_cluster   local://localhost?LRMS_TYPE=sge;PROJECT=l.project
+mycomputer  =  local://localhost?LRMS_TYPE=fork;NODECOUNT=2
+}}}
+{{{
+PBS_cluster =  local://localhost?LRMS_TYPE=pbs;QUEUE_NAME=estadistica;NODECOUNT=10
+}}}
+{{{
+SGE_cluster =  local://localhost?LRMS_TYPE=sge;PROJECT=l.project;NODECOUNT=40
 }}}
 If you want to configure a remote computing resource through ssh protocol, you need to put your private keys into your [[http://en.wikipedia.org/wiki/Ssh-agent|ssh-agent]], and it will handle your authentication thereafter (see [wiki:DRM4G#AppendixA Appendix A]) or set up SSH login without ''password'' (see [wiki:DRM4G#AppendixB Appendix B]). 
@@ -223 +226 @@
 In addition, you will probably need to update `WRF4G_BASEPATH`, `WRF4G_DOMAINPATH`, `WRF4G_INPUT` and `WRF4G_APPS` variables, which are defined in [wiki:WRF4Gresources_wrf4g  resources.wrf4g ]. Due to the fact that these variables may point to other machines. See [wiki:WRF4Gresources_wrf4g#Runningenvironment running environment ] for more information.
 {{{
-remote_PBS    ssh://user@meteo1.macc.unican.es?LRMS_TYPE=pbs;QUEUE_NAME=short
-}}}
-
-[[NoteBox(warn, After modifying `Computing Resources` section\, in order to make changes effective\, you have to execute: || `wrf4g_framework reload`)]] 
+remote_PBS  =  ssh://user@meteo1.macc.unican.es?LRMS_TYPE=pbs;QUEUE_NAME=short;NODECOUNT=10
+}}}
+
+[[NoteBox(warn, After modifying `ComputingResources` section\, WRF4G takes few seconds in order to update the changes)]]