Version 40 (modified by carlos, 10 years ago) (diff)


framework4g.conf file

The framework4g.conf file is read by wrf4g_framework to manage the WRF4G framework. It is located under $WRF4G_LOCATION/etc and has two sections, Database and Computing Resources.


WRF4G uses a MySQL database in order to keep track of the experiments. For that reason, WRF4G provides a 5.5-x86_64 distribution of MySQL under $WRF4G_LOCATION/opt/ directory. Also, you can use another MySQL changing WRF4G_DB_LOCAL variable.

You should modify the database password and WRF4G_DB_PASSWD variable after starting wrf4g_framework. To do that, you can execute:
echo "SET PASSWORD FOR 'wrf4guser'@'%' = PASSWORD('newpassword');" | mysql -P 13306 -u wrf4guser -h -p

0 indicates that you will use an external DB and the local database included in WRF4G distribution. If you want to use an external database, you will have to import WRF4GDB table in your MySQL.
Computer where the DB is running. If WRF4G_DB_LOCAL=1, WRF4G_DB_HOST has to be the name of the computer where WRF4G is running.
Port where mysql DB is listening.
Credentials to access DB
Name of the WRF4G DB

Computing Resources

WRF4G uses DRM4G in order to configure computing resources. Using that tool, users are able to access to different Distributed Resource Managements (DRM) such as:

  • PBS/Torque
  • SGE
  • FORK
  • LoadLeveler
  • MN SLRUM (only for Red Española de Supercomputación)
[Computing Resources]
#                                   HOST CONFIGURATION FILE
#                                   -----------------------
# Syntax
#   '#' Comments
# This file contains one resource per line, with format:
#   resource_name    attributes
#   ...     ...
#   resource_name    attributes
#   where:
#   * resource_name: is the name of the resource.
#   * attributes: are the static attributes of the resource. The 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 
#        -host: host name
#        -query: contains additional information. The query string syntax is:
#            * key1=value1;key2=value2;key3=value3
#            Variable options:
#               LRMS_TYPE   (mandatory)                : DRM system for execution [pbs | sge | fork | loadleveler | mnslurm ] 
#               PROJECT     (optional for SGE,         : specifies the project to which the jobs are assigned 
#                            PBS and LoadLeveler)
#               GW_RUNDIR   (optional)                 : directory on the resource in which jobs are deployed. By default, it is user's home
#               GW_LOCALDIR (optional)                 : defines the working directory on the Working Node (have to be an absolute path)
#               NODECOUNT   (optional)                 : total number of slots on the DRM system  
#               QUEUE_NAME  (optional)                 : the name of the queue to configure  
# Examples

mycomputer                   local://localhost?LRMS_TYPE=fork;NODECOUNT=1
#PBS_cluster                 local://localhost?LRMS_TYPE=pbs;QUEUE_NAME=estadistica
#SGE_cluster                 local://localhost?LRMS_TYPE=sge;PROJECT=l.project
#RES_cluster                 local://localhost?LRMS_TYPE=mnslurm
#remote_PBS_cluster          ssh://user@hostname_submitting_machine?LRMS_TYPE=pbs;QUEUE_NAME=short
#remote_SGE_cluster          ssh://user@hostname_submitting_machine?LRMS_TYPE=sge;PROJECT=l.project
#remote_RES_cluster          ssh://user@hostname_submitting_machine?LRMS_TYPE=mnslurm
#remote_FORK_cluster         ssh://user@hostname_submitting_machine?LRMS_TYPE=fork
#remote_LoadLeveler_cluster  ssh://user@hostname_submitting_machine?LRMS_TYPE=loadleveler;NODECOUNT=100

After modifying this file, in order to make changes effective, users will have to execute:
wrf4g_framework reload

More information regarding how to add resources on DRM4G.

Attachments (1)

Download all attachments as: .zip