Crab Server Integration with Glidein WMS

Architecture

1. glidein-2.t2.ucsd.edu = submitter with CRABSERVER
2. glidein-1.t2.ucsd.edu = gfactory
3. glidein-collector.t2.ucsd.edu = collector
4. glidein-frontend.t2.ucsd.edu = frontend, also runs a gcb under gcbuser account
5. glidein-gcb-1.t2.ucsd.edu = runs gcb under gcbuser account

The Crab Server is deployed at the machine (glidein-2.t2.ucsd.edu) with glideinWMS frontend's Schedd.

Relatively old but useful, details on glideinWMS at UCSD can be find here.

Crab Server Configuration

GUMS is used for mapping the user DN to local user at glidein-2.t2.ucsd.edu for remote crab client send data to and run jobs via crab server. Specifically

1. GUMS+PRIMA is integrated for the gridFTP that handles input of crab client's configuration data.
2. GUMS+glexec is integrated for the condor submission and glideinWMS.

The user proxy renewal and delegation are based on standard Crab Server deployment.

The condor jobs sent by the crab server go to the default schedd at glidein-2.t2.ucsd.edu.

Crab Client for Users

OR

source /afs/cern.ch/cms/ccs/wm/scripts/Crab/crab.sh

In your crab.cfg use:

 scheduler       = glidein

  server_name      = ucsd   

Job Monitoring @ UCSD

• CRABSERVER JobMon
• HTTP Frontend of the CS
• CMS Dashboard
• User task Monitoring using Dashboard

-- HaifengPi - 2008/11/10

-- SanjayPadhi - 2009/03/04