Version 29 (modified by carlos, 9 years ago) (diff)

--

# gwd.conf file

WRF4G Grid Resources are currently defined by GridWay Drivers. Therefore, if you want to access to Grid Resources, you must configure gwd.conf. This file is located under $WRF4G_LOCATION/opt/drm4g_gridway/etc directory. ## WRF4G GridWay Drivers Available The following drivers are included in WRF4G: • Information Driver: • BDII (gw_im_mad_bdii) • Transfer Driver: • Dummy Transfer driver (gw_tm_mad_dummy) • Execution Drivers: • GRAM2 (gw_em_mad_gram2) • CREAM (gw_em_mad_cream) ## Required Middleware The following middlewares should be installed to use the corresponding drivers: • Globus Toolkit 2 and above, and gLite 3.1 (GRAM2-based) • UMD1 or UMD2 (CREAM-based) ## Configuration options Divers Next steps describe a specific configuration of drivers for Gisela Infrastructure. However, the examples below can be applied to another VO. In file$WRF4G_LOCATION/opt/drm4g_gridway/etc/gwd.conf:

# Example MAD Configuration for GISELA
# GT2

# CREAM

There are two options for the configuration of IM MAD:

• -q: it is possible to configure a GridWay instance to only use queues authorized to your VO by filtering them.
• -s: information server in a hierarchical configuration.

There are two options for the configuration of the TM MAD:

• -g: starts a GASS server for each user.

• -u: specifies the URL of a GridFTP server running in the client. For example: