Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Include htcondor python bindings from conda-forge into 'stack'

Description

The BPS htcondor plugin will require the htcondor python bindings to function at S3DF (and elsewhere) . From examining
https://anaconda.org/conda-forge/htcondor
https://anaconda.org/conda-forge/htcondor/files
it appears that a suitable distribution for Python 3.10 should be available.
If this looks appropriate, requesting that the htcondor python bindings be included in 'the stack'.

Checklist

Lucidchart Diagrams

Issue Matrix

hide

Activity

Show:
Greg Daues
February 6, 2023 at 3:51 PM

This seems to be done.   Perhaps we can mark this ticket as done/complete. 

Greg Daues
November 9, 2022 at 4:27 PM

I do not think that the execute nodes actually need access to the htcondor python bindings from conda-forge.

If the bindings are in the base rubin-env environment, that would help in some broad cases, like users running at other sites conveniently having them in place, or more exotic scaling scenarios where parts of workflow run on a compute node. But for the initial base case of running at s3df, I do not think access on the execute nodes is needed.

Kian-Tat Lim
November 8, 2022 at 7:17 AM

This should really be an RFC, but I will try to get it into rubin-env 5.0.0 anyway.

My understanding is that this needs to be part of the user's conda environment for both submission and execution and as a result needs to be in the base rubin-env environment rather than rubin-env-rsp or rubin-env-developer. Is that correct?

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

RubinTeam

Components

Checklist

Created November 7, 2022 at 9:50 PM
Updated February 6, 2023 at 3:52 PM
Resolved February 6, 2023 at 3:52 PM