Skip to content
Snippets Groups Projects
Commit 3987c27d authored by Pavel Jirásek's avatar Pavel Jirásek
Browse files

Ext png for virtualization-job-workflow

parent 13a84b73
No related branches found
Tags
5 merge requests!368Update prace.md to document the change from qprace to qprod as the default...,!367Update prace.md to document the change from qprace to qprod as the default...,!366Update prace.md to document the change from qprace to qprod as the default...,!323extended-acls-storage-section,!88Content revision
Pipeline #
......@@ -47,7 +47,7 @@ IT4Innovations does not provide any licenses for operating systems and software
We propose this job workflow:
![Workflow](../../img/virtualization-job-workflow "Virtualization Job Workflow")
![Workflow](../../img/virtualization-job-workflow.png)
Our recommended solution is that job script creates distinct shared job directory, which makes a central point for data exchange between Anselm's environment, compute node (host) (e.g. HOME, SCRATCH, local scratch and other local or cluster file systems) and virtual machine (guest). Job script links or copies input data and instructions what to do (run script) for virtual machine to job directory and virtual machine process input data according instructions in job directory and store output back to job directory. We recommend, that virtual machine is running in so called [snapshot mode](virtualization/#snapshot-mode), image is immutable - image does not change, so one image can be used for many concurrent jobs.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment