Skip to content
Snippets Groups Projects
Commit 89544d20 authored by Lukáš Krupčík's avatar Lukáš Krupčík
Browse files

fix

parent 4440076d
No related branches found
No related tags found
No related merge requests found
# Singularity on IT4Innovations # Singularity on IT4Innovations
On clusters we have different versions of operating systems singularity images. Below you see the available operating systems singularity images. On clusters we have different versions of operating systems singularity images. Below you see the available operating systems singularity images.
Our images bootstrap, wrappers, features are [here](https://code.it4i.cz/sccs/it4i-singularity). Our images bootstrap, wrappers, features are [here](https://code.it4i.cz/sccs/it4i-singularity).
```console ```console
...@@ -27,11 +28,11 @@ For current information on available singularity images, refer to the `ml av` an ...@@ -27,11 +28,11 @@ For current information on available singularity images, refer to the `ml av` an
* Fedora * Fedora
!!! note !!! note
We support graphical cards on Anselm singularity image and support Intel Xeon Phi cards on Salomon images. (OS/Version-[none|GPU|MIC]) We support graphical cards on Anselm singularity image and support Intel Xeon Phi cards on Salomon images. (OS/Version[none|-GPU|-MIC])
## IT4Innovations Wrappers ## IT4Innovations Wrappers
For using modules we prepared special wrappers For using our singularity images we prepared special wrappers:
* image-exec * image-exec
* image-mpi * image-mpi
...@@ -46,7 +47,7 @@ Open image and run command into image. ...@@ -46,7 +47,7 @@ Open image and run command into image.
```console ```console
$ ml CentOS/7.3 $ ml CentOS/7.3
Your image of CentOS/7.3 is at location: /home/login/.singularity/images/CentOS-7.3_20180220104046.img Your image of CentOS/7.3 is at location: /home/login/.singularity/images/CentOS-7.3_20180220104046.img
image-exec cat /etc/centos-release $ image-exec cat /etc/centos-release
CentOS Linux release 7.3.1708 (Core) CentOS Linux release 7.3.1708 (Core)
``` ```
...@@ -56,11 +57,11 @@ MPI wrapper. More in the chapter [Examples MPI](#mpi) ...@@ -56,11 +57,11 @@ MPI wrapper. More in the chapter [Examples MPI](#mpi)
**image-run** **image-run**
Run subscript into image. Run subscript inside image.
**image-shell** **image-shell**
Start shell into image. Start shell inside image.
```console ```console
$ ml CentOS/7.3 $ ml CentOS/7.3
...@@ -101,21 +102,8 @@ $ ml CentOS/6.9 ...@@ -101,21 +102,8 @@ $ ml CentOS/6.9
Your image of CentOS/6.9 is at location: /home/login/.singularity/images/CentOS-6.9_20180220133305.img Your image of CentOS/6.9 is at location: /home/login/.singularity/images/CentOS-6.9_20180220133305.img
``` ```
!!! note !!! tip
First usage image copy image from /apps/all/OS/... to your /home (.singularity/images) First usage module with singularity image, copy singularity image from /apps/all/OS/... to your /home (.singularity/images)
For GPU and MIC images
```console
$ ml CentOS/6.9-GPU
```
```console
$ ml CentOS/6.9-MIC
```
!!! note
For the GPU image, you must allocate node with GPU card and for the MIC image, you must allocate node with the Intel Xeon Phi cards.
### Intel Xeon Phi Cards - MIC ### Intel Xeon Phi Cards - MIC
...@@ -144,9 +132,6 @@ int main() { ...@@ -144,9 +132,6 @@ int main() {
nthreads = std::thread::hardware_concurrency(); nthreads = std::thread::hardware_concurrency();
printf("Hello world from MIC, #of cores: %d\n",nthreads); printf("Hello world from MIC, #of cores: %d\n",nthreads);
} }
} }
``` ```
...@@ -222,7 +207,7 @@ By calling `mpirun` outside the container, we solve several very complicated wor ...@@ -222,7 +207,7 @@ By calling `mpirun` outside the container, we solve several very complicated wor
In the end, we do not gain anything by calling `mpirun` from within the container except for increasing the complexity levels and possibly losing out on some added performance benefits (e.g. if a container wasn’t built with the proper OFED as the host). In the end, we do not gain anything by calling `mpirun` from within the container except for increasing the complexity levels and possibly losing out on some added performance benefits (e.g. if a container wasn’t built with the proper OFED as the host).
### MPI Inside Image #### MPI Inside Image
```console ```console
$ ml CentOS/6.9 $ ml CentOS/6.9
...@@ -236,7 +221,7 @@ Singularity CentOS-6.9_20180220092823.img:~> mpirun hostname | wc -l ...@@ -236,7 +221,7 @@ Singularity CentOS-6.9_20180220092823.img:~> mpirun hostname | wc -l
!!! warning !!! warning
You allocate two nodes, but MPI inside image use only one node. You allocate two nodes, but MPI inside image use only one node.
### MPI Outside Image #### MPI Outside Image
```console ```console
$ ml CentOS/6.9 $ ml CentOS/6.9
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment