Changes between Version 83 and Version 84 of WRF4GTutorial2
- Timestamp:
- Mar 31, 2013 2:55:28 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WRF4GTutorial2
v83 v84 179 179 * FORK 180 180 * !LoadLeveler 181 * MN SLURM (only for Red Española de Supercomputación)181 * SLURM 182 182 183 In order to add new resources, you need to edit `Computing 184 185 {{{ 186 resource_name attributes183 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: 184 185 {{{ 186 resource_name = attributes 187 187 ... ... 188 resource_name attributes188 resource_name = attributes 189 189 }}} 190 190 191 191 where: 192 * '''resource_name''': is the name of theresource.193 * '''attributes''': are the static attributes of the resource and theirsyntax is:194 * `<scheme>://<username>@<host >?<query>`195 * '''scheme''': theURL schemes available are "ssh" and "local".196 * '''ssh''': access to remote DRMvia SSH197 * '''local''': use the local DRM198 * '''username''': user name 192 * '''resource_name''': It is the name of the computing resource. 193 * '''attributes''': They are the static attributes of the computing resource. The syntax is: 194 * `<scheme>://<username>@<host:port>?<query>` 195 * '''scheme''': URL schemes available are "ssh" and "local". 196 * '''ssh''': In order to connect to remote resource via SSH 197 * '''local''': In order to use a local resource 198 * '''username''': user name on the resource 199 199 * '''host''': host name 200 * '''query''': contains additional information. The query string syntax is: 200 * '''port''': host port to connect to. By DEFAULT is 2 201 * '''query''': contains additional information of computing resources. The query string syntax is: 201 202 * key1=value1;key2=value2;key3=value3 202 203 203 204 The keys available are: 204 * '''LRMS_TYPE'''(mandatory): DRM system for execution [pbs | sge | fork | loadleveler | mnslurm ] 205 * '''PROJECT'''(optional for SGE, PBS and !LoadLeveler): specifies the user's project on the computing resource 206 * '''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) 207 * '''GW_LOCALDIR'''(optional): defines the working directory on the computing resource (have to be an absolute path) 208 * '''NODECOUNT'''(optional): total number of slots on the DRM system (cores) 209 * '''QUEUE_NAME'''(optional): the name of the queue to configure 205 * '''LRMS_TYPE'''(mandatory): Type of LRMS system [pbs | sge | fork | slurm ] 206 * '''NODECOUNT'''(mandatory): Maximum number of job slots for a resource. 207 * '''QUEUE_NAME'''(mandatory): Queue name to configure. It is mandatory except for "LRMS_TYPE=fork" 208 * '''SSH_KEY_FILE'''(optional): It defines the key file for "ssh" connection. By DEFAULT is ~/.ssh/id_rsa. 209 * '''PROJECT'''(optional): It specifies the project which the jobs are assigned. It is only optional for SGE and PBS. 210 * '''PARALLEL_TAG'''(optional): It defines the parallel environments available for SGE. 211 * '''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. 212 * '''RUN_DIR'''(optional): Temporary directory used to run WRF Model on the resource. By DEFAULT is $HOME. RUN_DIR path must be absolute. 210 213 211 214 Examples of configuration: 212 215 {{{ 213 mycomputer local://localhost?LRMS_TYPE=fork;NODECOUNT=2214 }}} 215 {{{ 216 PBS_cluster local://localhost?LRMS_TYPE=pbs;QUEUE_NAME=estadistica217 }}} 218 {{{ 219 SGE_cluster local://localhost?LRMS_TYPE=sge;PROJECT=l.project216 mycomputer = local://localhost?LRMS_TYPE=fork;NODECOUNT=2 217 }}} 218 {{{ 219 PBS_cluster = local://localhost?LRMS_TYPE=pbs;QUEUE_NAME=estadistica;NODECOUNT=10 220 }}} 221 {{{ 222 SGE_cluster = local://localhost?LRMS_TYPE=sge;PROJECT=l.project;NODECOUNT=40 220 223 }}} 221 224 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. 224 227 {{{ 225 remote_PBS ssh://user@meteo1.macc.unican.es?LRMS_TYPE=pbs;QUEUE_NAME=short226 }}} 227 228 [[NoteBox(warn, After modifying `Computing Resources` section\, in order to make changes effective\, you have to execute: || `wrf4g_framework reload`)]]228 remote_PBS = ssh://user@meteo1.macc.unican.es?LRMS_TYPE=pbs;QUEUE_NAME=short;NODECOUNT=10 229 }}} 230 231 [[NoteBox(warn, After modifying `ComputingResources` section\, WRF4G takes few seconds in order to update the changes)]] 229 232 230 233