[HTCondor-devel] Contributing to HTCondor


Date: Thu, 02 Nov 2017 18:06:08 +0100
From: Oliver Freyermuth <freyermuth@xxxxxxxxxxxxxxxxxx>
Subject: [HTCondor-devel] Contributing to HTCondor
Dear developers,

since my last question might have been too specialized for others to find (especially in htcondor-users),
I'm now asking in a more generic manner on the devel mailing list. 

What's the best way to get started with HTCondor development, and in which way are contributions expected? 

I would be interested in writing a charliecloud "plugin" (very much like the singularity plugin, only the wrapper and of course some parameters
are different / do not exist). 
Looking at the way the singularity plugin implementation is done, the procedure seems straightforward. 

Background and reasoning (already explained on the htcondor-users list):
Charliecloud should allow to easily resolve the condor_ssh_to_job issue,
since an unprivileged "nsenter" call is sufficient to enter the container. This could be done via the authorized-keys injection or ForceCommand. 
So as Cluster-admin it would be my first choice in terms of security (no setuid root / no root daemon) whenever user namespaces are sufficient,
especially since it can run extracted containers built with docker or singularity, so no new work is needed. 
That's why I'd like to see it supported in HTCondor, but of course nothing comes for free, so I'm offering to implement things. 

Do I simply get started, at some point submit a PR on github / a mail here, and then we discuss implementation details? 
Or is there another preferred way? 

Or is somebody else interested in it / already working on that? 

Cheers,
Oliver


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

[← Prev in Thread] Current Thread [Next in Thread→]
  • [HTCondor-devel] Contributing to HTCondor, Oliver Freyermuth <=