# Presentation: 813307

## Computing on Demand

- February 5, 2004

## Status of Condor at RACF

- Condor 6.6.0 installed on all 1097 Linux Farm nodes in RACF.
- Standard batch policy in place (fair-share, job suspension, etc).
- Multiple queues for CAS & CRS, sub-divided by experiments.

## Changes Since Initial Install

- Graphical package (condorview) installed and running. Needs external Web server access.
- Strong authentication for Condor in progress (Kerberos and GLOBUS certificates).
- Fail-over feature to be available soon?
- Computing on Demand (COD) feature enabled.

## Computing on Demand

- COD allows users to submit high-priority jobs with interactive-like response.
- COD jobs do not follow standard Condor batch policies (jobs run immediately after submission).
- COD jobs suspend standard Condor & LSF jobs.
- COD job description file (jdf) is different from standard Condor jdf’s.

## Computing on Demand (cont.)

- COD only available to pre-defined list of privileged users.
- Currently only the “reco” accounts are in the list.
- Request for additional users with COD privilege must originate from RACF Liaison.

## Computing on Demand (cont.)

- Privileged users must first request COD resources (see below):
- >  condor_cod request -name <hostname> [-pool condor01.rcf.bnl.gov:<port>] -classad cod.id
- > Successfully sent CA_REQUEST_CLAIM to startd at <130.199.206.51:32787>
- > Result ClassAd written to cod.id
- > ID of new claim is: “<130.199.206.51:32787>#1071856759#1”

## Computing on Demand (cont.)

- Hostname is FQDN (Fully Qualified Domain Name).
- Ports (optional parameter) are as follows:
-                                               9660  ATLAS
-                                               9661  BRAHMS
-                                               9662  PHENIX
-                                               9663  PHOBOS
-                                               9664  STAR
-                                               9665  RCF

## Computing on Demand (cont.)

- Next, privileged user must activate his/her COD claim (which runs the COD job contained in cod.job):
- >  condor_cod activate -id “<130.199.206.51:32787>#1071856759#1” -jobad cod.job
- > Successfully sent CA_ACTIVATE_CLAIM to startd at <130.199.206.51:32787>

## Computing on Demand (cont.)

- Users can check on progress of their COD jobs with:
- >  condor_status [-pool condor01.rcf.bnl.gov:<port>] -cod
- Name          ID         ClaimState  TimeInState  RemoteUser  JobId  Keyword
- >  vm2@rcas6001  COD1  Running  0:00:06:46  starreco  1.0
-                  Total  Idle  Running  Suspended  Vacating  Killing
- >  INTEL/LINUX    1	0	1	0	0	0
- >  TOTAL	    1	0	1	0	0	0

## Computing on Demand (cont.)

- Privileged users can release COD resource upon completion of their COD jobs:
- >  condor_cod release [-pool condor01.rcf.bnl.gov:<port>] -id “<130.199.206.51:32787>#1071856759#1”
- >  Successfully sent CA_RELEASE_CLAIM to startd at <130.199.206.51:32787>
- >  Status of claim when it was released: “Idle”

## Computing on Demand (cont.)

- Examples of COD jdf’s can be found in:
- /usatlas/u/atlareco/condor/cod.job
- /brahms/u/bramreco/condor/cod.job
- /phenix/u/phnxreco/condor/cod.job
- /phobos/u/phobreco/condor/cod.job
- /star/u/starreco/condor/cod.job

## What’s next?

- Plan is to implement COD this week on fastest CAS servers within each experiment.
- Maybe also implement on CRS servers for new CRS Batch software?
- Attend Condor Week (April 15-16, 2004) in Madison to learn how to improve our Condor pool. We have many questions...