Feature #24407
Support CVMFS and Singularity when none of the 2 is available on the worker node
Start date:
05/13/2020
Due date:
% Done:
0%
Estimated time:
Stakeholders:
CMS
Description
Sometimes CVMFS is not available and Singularity neither.
The Glidein should be able to connect to CVMFS and start Singularity from there.
There are some possibility, from Dave:
1. mountrepo/umountrepo only • requires fusermount; mounts in user space • map /cvmfs in container with singularity –bind (not run from cvmfs because of path) 2. cvmfsexec on RHEL 7.6 or 7.7 • requires fusermount and additionally unprivileged user namespaces enabled • maps /cvmfs without singularity, can run singularity under it • unmounts repos on exit, but not with kill -9 3. cvmfsexec on RHEL >= 7.8 • no fusermount needed, and cleans up mounts even with kill -9 • still needs unprivileged user namespaces enabled; that is default on RHEL 8 4. singcvmfs on any system with singularity >= 3.4.0 • drop-in replacement for singularity; set environment variable with cvmfs repos to mount • requires container image to already be present (not read from cvmfs) • requires setuid-root singularity except when RHEL >= 7.8 and and singularity >= 3.6.0Consider also
- package building (at reconfig/upgreade)
- proxy search and setup (WPAD)
Related issues
History
#1 Updated by Marco Mambelli 8 months ago
- Related to Milestone #19515: Roadmap for Singularity support added
#2 Updated by Marco Mambelli 8 months ago
- Priority changed from Normal to High
- Description updated (diff)
- Subject changed from Support CVMFS and Singularity when none of the 2 is available to Support CVMFS and Singularity when none of the 2 is available on the worker node
#3 Updated by Marco Mambelli 7 months ago
CVMFS support has been moved to [#24546], specified in more detail
#4 Updated by Marco Mambelli 7 months ago
- Blocked by Feature #24546: Add the ability to use CVMFS on sites that do not provide local installations added
#5 Updated by Marco Mambelli 4 months ago
- Target version changed from v3_6_4 to v3_6_5
#6 Updated by Marco Mambelli 4 months ago
- Target version changed from v3_6_5 to v3_6_6
#7 Updated by Marco Mambelli 4 months ago
- Target version changed from v3_6_6 to v3_6_7