Feature #21886
Custom modules for job wrappers
Start date:
02/11/2019
Due date:
% Done:
0%
Estimated time:
Stakeholders:
Description
Currently, the support for user job wrappers in GlideinWMS allows multiple wrappers but they are "cat" one after the other without control and coordination.
The first one exec-ing the job (like wrappers normally do) is then interrupting the chain.
The idea is to allow VO to have custom wrappers that are loaded as modules by the GlideinWMS job wrapper
Ideally, these modules could run outside and/or inside Singularity (the container)
This would be especially useful to implement pre-job tests when using Singularity.
Related issues
History
#1 Updated by Marco Mambelli about 2 years ago
- Related to Milestone #19515: Roadmap for Singularity support added
#2 Updated by Marco Mambelli over 1 year ago
- Assignee set to Marco Mambelli
#3 Updated by Marco Mambelli over 1 year ago
- Target version changed from v3_5_x to v3_6_1
#4 Updated by Marco Mambelli over 1 year ago
- Target version changed from v3_6_1 to v3_6_2
#5 Updated by Marco Mambelli about 1 year ago
- Target version changed from v3_6_2 to v3_6_3
#6 Updated by Marco Mambelli 11 months ago
- Target version changed from v3_6_3 to v3_6_4
#7 Updated by Marco Mambelli 7 months ago
- Target version changed from v3_6_4 to v3_6_5
#8 Updated by Marco Mambelli 6 months ago
- Target version changed from v3_6_5 to v3_6_6
#9 Updated by Marco Mambelli 4 months ago
- Target version changed from v3_6_6 to v3_6_7
#10 Updated by Marco Mambelli 2 months ago
- Target version changed from v3_6_7 to v3_7_4