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

Database

You should modify the database password after starting wrf4g_framework. You can execute:

echo "SET PASSWORD FOR 'wrf4guser'@'%' = PASSWORD('newpassword');" | mysql -P 11002 -u wrf4guser -h 127.0.0.1 -p

[Database]
WRF4G_DB_LOCAL=1
WRF4G_DB_HOST=mycomputer
WRF4G_DB_PORT=13306
WRF4G_DB_USER="wrf4guser"
WRF4G_DB_PASSWD="Meteo2011"
WRF4G_DB_DATABASE="WRF4GDB"

WRF4G_DB_LOCAL

0 indicates we want to use a external DB, 1 local.

WRF4G_DB_HOST

Computer where DB is running. If WRF4G_DB_LOCAL=1, WRF4G_DB_HOST has to be the name of the computer where WRF4G is running.

WRF4G_DB_PORT

Port where mysql DB is listening.

WRF4G_DB_USER and WRF4G_DB_PASSWD

Credentials to access DB

WRF4G_DB_DATABASE

Name or the WRF4G DB

Computing Resources

The following code shows the syntax to add resources.

[Computing Resources]
#**********************************************************************************************
#                                   HOST CONFIGURATION FILE
#                                   -----------------------
# Syntax
#   '#' Comments
#
# This file contains one resource per line, with format:
#
#   FQDN    attributes
#   ...     ...
#   FQDN    attributes
#
#   where:
#   
#   * FQDN: 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)                 : the directory on the resource in which jobs are deployed. By default, it is the user's home
#               GW_LOCALDIR (optional)                 : defines the working directory on the Working Node (have to be 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 the changes effective, users will have to execute: wrf4g_framework reload

More information about how to add resources on DRM4G.