GRAM5 In EGI

A computing element (CE) in the EGI is far more than an interface to submit jobs: the ecosystem has a lot of implicit assumptions as to what a CE is supposed to do, the set of services that it should run, the information it should publish in a variety of formats, and the programs that have to be installed on the CE itself to 'play nice' with the other EGI services. In this writeup, we attempt to document what needs to be done to turn the basic GRAM5 CE into a service which integrated with EGI. To do this, we use the GRAM5 service from the Initiative for Globus in Europe (IGE), as well as other components distributed via the EGI UMD repository.

Goals of the GRAM5 CE

The GRAM5 service we have in mind should support the following:

• provide a GRAM5/GRAM2 compatible submission interface (what you get from IGE gram5 proper)
• resemble the LCG-CE application interface
• be visible to end-users using lcg-infosites
• be visible to the EMI Workload Management System (WMS) and 'automatically' attract jobs for supported VOs
• interoperate with GLUE2 information system clients
• support legacy GLUE1.3 (mainly for the WMS and lcg-infosites)
• support all IGTF CAs and honour CRLs
• fully support VOMS FQAN mappings and poolaccounts
• also allow local accounts to be used in conjunction with (and override) VOMS FQANs
• be configured for scalability using the Scheduler Event Generator (SEG)
• be resilient to users: use TMPDIR as default home, and find executables using PATH
• support accounting output in NDPF (CREAMy) compatible form
• log details in conformance to the CSIRT requirements

Requisite software

Install either "ige-meta-globus-gram5-2.1-1.el5.noarch.rpm" and then remove the superfluous packages, or install the list of RPMs for basic GRAM5.

Lists and templates

RPM package lists

Superfluous packages in IGE meta-package for GRAM5

The following packages are not needed for proper functioning, once you already have a functioning bacth system client setup. You will not need client and server tools for each and every scheduler in the world. Install your own favourite version of a batch system and be content. Also: only install the batch system plugins for the jobmanager that you really need:

fedora-usermgmt
fedora-usermgmt-core
fedora-usermgmt-default-fedora-setup
fedora-usermgmt-shadow-utils

gridengine
libtorque
munge
munge-libs
torque
torque-client

and after installing your own batch system client, pickone of

globus-gram-job-manager-condor
globus-gram-job-manager-pbs
globus-gram-job-manager-sge

or they'll complain about missing dependencies.