Interoperation of GridWay with the EGI infrastructure

The gLite middleware was developed by the EGEE project and it is currently supported by EMI and used in EGI as part of UMD. It provides different grid services, such as BDII (Berkeley Database Information Index) which is an information system for grid computing infrastructures, and CREAM (Computing Resource Execution And Management) which is a simple, lightweight service for job management. CREAM is currently used as the official job submission interface on EGI.

• Install the UMD2 repository provided by EGI.

• Install the gridway-gLite package that provides the gLite drivers for GridWay. UMD2 repository must resolve all dependencies.

• Alternatively, you can build and install the CREAM, BDII and dummy drivers by yourself. Install glite-ce-cream-client-devel package to build the drivers.

The GridWay Configuration Guide provides complete information about configuration of the meta-scheduler. Next steps describe the specific configuration of the gLite access drivers.

• Add the following lines in the /usr/etc/gwd.conf file:

  IM_MAD = bdii:gw_im_mad_bdii:-s <bdii-server> -q (GlueCEAccessControlBaseRule=VO\:<VO>)(GlueCEImplementationName=CREAM):dummy:cream
  EM_MAD = cream:gw_em_mad_cream::jdl
  TM_MAD = dummy:gw_tm_mad_dummy:-g

Don't forget to set up <bdii-server> and <VO> with a BDII server and a VO that grants you access to resources.

• Some privileges are required to be set in the /etc/sudoers file. Please add the following lines.

   Defaults>GWUSERS env_keep="GW_LOCATION GLOBUS_LOCATION"
   #GridWay entries (gLite MAD)
   gwadmin ALL=(GWUSERS) NOPASSWD: /usr/bin/gw_im_mad_bdii *
   gwadmin ALL=(GWUSERS) NOPASSWD: /usr/bin/gw_em_mad_cream *
   gwadmin ALL=(GWUSERS) NOPASSWD: /usr/bin/gw_tm_mad_dummy *

The functionality and interfaces provided by GridWay are independent from the underlying Grid infrastructure. Please refer to the guides (user's guide, command reference, programming guide…) available at the Documentation section.