Changes between Version 3 and Version 4 of WRF4Gframework4g_conf


Ignore:
Timestamp:
Sep 7, 2011 1:39:50 PM (11 years ago)
Author:
valva
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WRF4Gframework4g_conf

    v3 v4  
     1framework4g.conf is read by '''[wiki:WRF4GCommandLineTools#wrf4g_framework wrf4g_framework]''' to manage the WRF4G framework. framework4g.conf is located under $WRF4G_LOCATION/etc.
    12
    2 == Manage WRF4G Framework ==
    3 WRF4G framework allows us to define all the computing resources we have access to (clusters, grid infrastructures, single computers...). Given this list of resources, when we run an experiment, we can let framework choose the resources for us, or we can indicate the requirements our experiment has (we may want to run an experiment in a given resource). This resource management is done through [https://meteo.macc.unican.es/trac/WRF4G/wiki/DRM4G DRM4G].
    4 In order to trac the experiment status, WRF4G framework has also a database that handle all the events experiments generate. The only thing users should know about this database is that it have to be running all the time.
     3It has 2 section, Database and Computing Resources.
    54
    6 Framework can be started and stopped with the following command: '''wrf4g_framework start/stop/restart'''. Note that the WRF4G environment variables have to be set.
    7 {{{
    8 export WRF4G_LOCATION=$install_path/WRF4G
    9 export GW_LOCATION=$WRF4G_LOCATION/opt/drm4g_gridway-5.7
    10 export PATH=$WRF4G_LOCATION/bin:$GW_LOCATION/bin:$PATH
    11 }}}
    12 
    13 
    14 The WRF4G framework is configured in the file '''framework4g.conf''' (located in $WRF4G_LOCATION/etc). It is divided in to sections: Database and Computing Resources.
    15  * '''Database''': Defines the database access configuration. Note that in order to the experiments to work properly it's necesary to have access from the computing resource to the 13306 port of the server where Database is running. If you encounter firewall problems, you can change the port.
    16  * '''Computing Resources''': List of Computing resources. For more information see [https://meteo.macc.unican.es/trac/WRF4G/wiki/DRM4G DRM4G].
    17 
     5== Database ==
    186{{{
    197[Database]
    20 DB_HOST="$HOSTNAME"
     8DB_LOCAL=1
     9DB_HOST=sipc18
    2110DB_PORT=13306
    2211DB_USER="wrf4guser"
    2312DB_PASSWD="Meteo2011"
    2413DB_WRF4G="WRF4GDB"
     14}}}
    2515
    26 [Computing Resources]
     16DB_LOCAL
     17  0 indicates we want to use a external DB, 1 local.
     18DB_HOST
     19  Computer where DB is running. If DB_LOCAL=1, DB_HOST has to be the name of the computer where WRF4G is running.
     20DB_PORT
     21  Port where mysql DB is listening.
     22DB_USER and DB_PASSWD
     23  Credentials to access DB
     24DB_WRF4G
     25  Name or the WRF4G DB
     26
     27
     28== Computing Resources ==
     29The following code shows the sintaxis to add resources.
     30{{{
     31#**********************************************************************************************
     32#                                   HOST CONFIGURATION FILE
     33#                                   -----------------------
     34# Syntax
     35#   '#' Comments
     36#
     37# This file contains one resource per line, with format:
     38#
     39#   FQDN    attributes
     40#   ...     ...
     41#   FQDN    attributes
     42#
     43#   where:
     44#   
     45#   * FQDN: is the name of resource.
     46#   * attributes: are the static attributes of resource. The syntax is:
     47#
     48#        <scheme>://<username>@<host>?<query>
     49#
     50#        -scheme: the URL schemes available are "ssh" and "local".
     51#            * ssh:   access to remote DRM via SSH
     52#            * local: use the local DRM
     53#        -username: user name
     54#        -host: host name
     55#        -query: contains additional information. The query string syntax is:
     56#            * key1=value1;key2=value2;key3=value3
     57#            Variable options:
     58#               LRMS_TYPE   (mandaroty)        : type of local DRM system for execution [pbs | sge | fork | mnslurm ]
     59#               PROJECT     (optional for SGE) : specifies the project to which the jobs are assigned
     60#               GW_RUNDIR   (optional)         : defines the working directory on the DRM system and must be absolute path
     61#               GW_LOCALDIR (optional)         : defines the working directory on the Working Node
     62#               NODECOUNT   (optional)         : total number of slots on the DRM system 
     63#               QUEUE_NAME  (optional)         : name of the queue to configure. 
     64#*********************************************************************************************
     65# Examples
     66
    2767mycomputer            local://localhost?LRMS_TYPE=fork;NODECOUNT=1
    2868#PBS_cluster          local://localhost?LRMS_TYPE=pbs;QUEUE_NAME=estadistica
    2969#SGE_cluster          local://localhost?LRMS_TYPE=sge;PROJECT=l.project
    3070#RES_cluster          local://localhost?LRMS_TYPE=mnslurm
     71#remote_PBS_cluster   ssh://user@hostname_submitting_machine?LRMS_TYPE=pbs;QUEUE_NAME=short
     72#remote_SGE_cluster   ssh://user@hostname_submitting_machine?LRMS_TYPE=sge;PROJECT=l.project
     73#remote_RES_cluster   ssh://user@hostname_submitting_machine?LRMS_TYPE=mnslurm
     74#remote_FORK_cluster  ssh://user@hostname_submitting_machine?LRMS_TYPE=fork
     75
    3176}}}
     77
     78
     79More information about how to add resources on [wiki:DRM4G DRM4G].