wiki:WRF4GGridConfiguration

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 
IM_MAD = gisela_gt2:gw_im_mad_bdii:-q (GlueCEAccessControlBaseRule=VO\:prod.vo.eu-eela.eu)(GlueCEImplementationName=LCG-CE)  -s bdii.eela.ufrj.br:tm_gt2:em_gt2
EM_MAD = em_gt2:gw_em_mad_gram2::rsl_nsh
TM_MAD = tm_gt2:gw_tm_mad_dummy:-u gsiftp\://ui01.macc.unican.es

# CREAM
IM_MAD = gisela_cream:gw_im_mad_bdii:-q (GlueCEAccessControlBaseRule=VO\:prod.vo.eu-eela.eu)(GlueCEImplementationName=CREAM)  -s bdii.eela.ufrj.br:tm_cream:em_cream
EM_MAD = em_cream:gw_em_mad_cream.py::jdl
TM_MAD = tm_cream:gw_tm_mad_dummy:-u gsiftp\://ui01.macc.unican.es

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.
    IM_MAD = glisela_gt2:gw_im_mad_bdii:-q (GlueCEAccessControlBaseRule=VO\:prod.vo.eu-eela.eu)(GlueCEImplementationName=LCG-CE) -s bdii.eela.ufrj.br:tm_gt2:em_gt2
    

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

  • -g: starts a GASS server for each user.
    TM_MAD = tm_gt2:gw_tm_mad_dummy:-g
    
  • -u: specifies the URL of a GridFTP server running in the client. For example:
    TM_MAD = tm_gt2:gw_tm_mad_dummy:-u gsiftp\://ui01.macc.unican.es
    

For more information about MAD configuration see GridWay Configuration Guide

After modifying gwd.log, in order to make changes effective, you have to execute:
wrf4g_framework reload

Then, you must check resources.wrf4g file, in order to configure the Grid running environment

Accessing the VOMS servers

In order to use the Grid Resources, users should initialize the proxy through voms server:

[user@ui~]$ voms-proxy-init --voms prod.vo.eu-eela.eu
Cannot find file or dir: /oceano/gmeteo/users/carlos/.glite/vomses
Enter GRID pass phrase:
Your identity: /DC=es/DC=irisgrid/O=unican/CN=josecarlos.blanco
Creating temporary proxy ........................................ Done
Contacting  voms.eela.ufrj.br:15003 [/C=BR/O=ICPEDU/O=UFF BrGrid CA/O=UFRJ/OU=IF/CN=host/voms.eela.ufrj.br] "prod.vo.eu-eela.eu" Done
Creating proxy ................................... Done
Your proxy is valid until Tue Aug 23 22:15:06 2011
Last modified 7 years ago Last modified on Apr 2, 2013 1:39:53 PM