This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
lcrc:introduction [2019/01/22 14:42] asc [Using singularity] |
lcrc:introduction [2023/04/27 19:18] asc [Using Singularity for cvmfsexec] |
||
---|---|---|---|
Line 108: | Line 108: | ||
<code bash> | <code bash> | ||
- | srun --pty -p bdwall | + | srun --pty -p bdwall |
</ | </ | ||
Line 132: | Line 132: | ||
To run on non HEP nodes use partition bdwall with Account - ATLAS-HEP-group | To run on non HEP nodes use partition bdwall with Account - ATLAS-HEP-group | ||
- | ==== Using Singularity | + | |
+ | ==== Using interactive jobs ==== | ||
+ | |||
+ | |||
+ | First, allocate a HEP node: | ||
+ | |||
+ | <code bash> | ||
+ | salloc -N 1 -p hepd -A condo -t 00:30:00 | ||
+ | </ | ||
+ | |||
+ | This allocates it for 30 min, but you can allocate it up to 7 days. | ||
+ | You cam also allocate it on bebob: | ||
+ | |||
+ | <code bash> | ||
+ | salloc -N 1 -p bdwall --account=ATLAS-HEP-group -t 00:30:00 | ||
+ | </ | ||
+ | |||
+ | This does not login you! | ||
+ | Check what node did you allocate | ||
+ | |||
+ | <code bash> | ||
+ | squeue -u user | ||
+ | </ | ||
+ | |||
+ | |||
+ | Now you know the node. Then login to bebob (first!) and then ssh to this node. | ||
+ | |||
+ | Another method is to use | ||
+ | |||
+ | <code bash> | ||
+ | srun --pty -p bdwall | ||
+ | </ | ||
+ | |||
+ | |||
+ | === Running long interactive jobs === | ||
+ | |||
+ | See more description in: https:// | ||
+ | |||
+ | You should be able to do for example: | ||
+ | |||
+ | < | ||
+ | -ssh bebop | ||
+ | -screen | ||
+ | -salloc -N 1 -p hepd -A condo -t 96:00:00 | ||
+ | -ssh < | ||
+ | -Work on interactive job for x amount of time... | ||
+ | -Disconnect from screen (different than exit, see the documentation) | ||
+ | -Logout | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | -Login to the same login node screen was started on | ||
+ | -screen -ls | ||
+ | -Connect to screen session | ||
+ | -Continue where you left off (if they allocation is still active) | ||
+ | </ | ||
+ | |||
+ | See below for more details: | ||
+ | |||
+ | https:// | ||
+ | |||
+ | https:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ====== Using Singularity ====== | ||
To run jobs on all LCRC resources using ATLAS analysis base requires Docker/ | To run jobs on all LCRC resources using ATLAS analysis base requires Docker/ | ||
| | ||
+ | |||
+ | Here are the suggested steps for 21.2.51 release. | ||
+ | |||
+ | < | ||
+ | docker pull atlas/ | ||
+ | </ | ||
+ | |||
+ | Then make singularity image: | ||
+ | <code bash> | ||
+ | docker run -v / | ||
+ | </ | ||
+ | |||
+ | |||
+ | Currently, the image for AtlasBase 2.2.51 located here: | ||
+ | |||
+ | < | ||
+ | / | ||
+ | </ | ||
+ | |||
+ | You can go inside this image as: | ||
+ | |||
+ | < | ||
+ | singularity exec / | ||
+ | </ | ||
+ | |||
+ | ====== Using Singularity for cvmfsexec ====== | ||
+ | |||
+ | One can also setup cvmf on any LCRC nodes as this: | ||
+ | < | ||
+ | source / | ||
+ | </ | ||
+ | |||
+ | Then check: | ||
+ | < | ||
+ | ls /cvmfs/ | ||
+ | </ | ||
+ | |||
+ | You will see the mounted directory (SL7): | ||
+ | < | ||
+ | atlas-condb.cern.ch/ | ||
+ | atlas-nightlies.cern.ch/ | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
+ | |||
- | --- // | + | --- // |