The WRF4G Framework is a set of daemons/services that, on the one hand, manage the Computing Resources where WRF is going to run, and, on the other hand, manage the experiment information and status (realization, chunks, jobs).
During the installation process, the WRF4G Framework is configured by default and it can be run without doing any change in the configuration.
WRF4G framework is managed with the command wrf4g_framework. With this command we can start, stop and reload the framework.
Note that wrf4g_framework is a daemon that has to be running if we want to perform an experiment.
WRF4G framework allows us to define all the computing resources that we have access to (clusters, grid infrastructures, single computers...). Given a 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).
The WRF4G framework is configured to use a single resource by default (the computer where WRF4G has been installed). In order to add more resources, users have to list them in the Computing Resources section of framework4g.conf (See framework4g.conf to get more information about adding resources). After modifying this file, in order to make the change effective, users will have to reload the framework with the following command wrf4g_framework reload
WRF4G framework uses a database that store the experiments information and status. This database is configured by default in the WRF4G installation and it should work without any modification. The DB configuration is set in the Database section of framework4g.conf (See framework4g.conf to get more information about configuring Database)
Note that DB_PORT of UI has to be reachable from the Computing Resources (to update the experiment information). Therefore, DB_PORT has to be open in the firewall.