Version 1 (modified by carlos, 9 years ago) (diff) |
---|
How to add new Neptuno facilities to WRF4G
WRF4G uses DRM4G to access to different Distributed Resource Managements (DRM) such as:
- PBS/Torque
- SGE
- FORK
- LoadLeveler
- SLURM
In order to add new resources, you need to edit ComputingResources section in the 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
where:
- 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
- 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
- scheme: URL schemes available are "ssh" and "local".
- <scheme>://<username>@<host:port>?<query>
The keys available are:
- 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 on the resource to 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:
If you want to configure a remote computing resource through ssh protocol, you need to put your private keys into your ssh-agent, and it will handle your authentication thereafter (see Appendix A) or set up SSH login without password (see Appendix B).
In addition, you will probably need to update WRF4G_BASEPATH, WRF4G_DOMAINPATH, WRF4G_INPUT and WRF4G_APPS variables, which are defined in resources.wrf4g . Due to the fact that these variables may point to other machines. See running environment for more information.
remote_PBS = ssh://userid@193.144.213.182?LRMS_TYPE=neptuno;NODECOUNT=1500
After modifying ComputingResources section, WRF4G takes few seconds in order to update the changes