Project

General

Profile

Feature #21711

Add a portable condor_chirp for jobs running under GlideinWMS

Added by Marco Mambelli 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
01/16/2019
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

GlideinWMS does include condor_chirp
As requested by CMS [#6424], [#6430] to allow jobs to use CHIRP.
With the introduction of Singularity condor_chirp is not always available:
- the new environment may hide the Glidein condor to the job
- the job may run on a different platform (e.g. Glidein uses base OS, EL7, and job asks for and runs in EL6)

Some VOs ran into errors while trying to use the Glidein provided condor_chirp

A solution could be to download and make available a basic condor for the platform of the Singularity image, or make always available binaries for a set of platform or provide a multy-platform client (e.g. the python client https://github.com/htcondor/htchirp )


Related issues

Related to glideinWMS - Milestone #19515: Roadmap for Singularity supportNew2018-03-27

History

#1 Updated by Marco Mambelli 3 months ago

As from an email from Jaime:

ssh-to-job and chirp should work with singularity jobs. For chirp, the singularity image will need to include a chirp client. There are several options for this:
  + The condor_chirp tool, which depends on the condor and classad libraries.
  + A pure python module, available here: https://github.com/htcondor/htchirp
  + Write your own client, as documented here: http://ccl.cse.nd.edu/software/chirp/

#2 Updated by Marco Mambelli 2 months ago



Also available in: Atom PDF