From 3987c27d470af32ef07b2e15b513f4b716bf93e4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pavel=20Jir=C3=A1sek?= <pavel.jirasek@vsb.cz>
Date: Wed, 1 Feb 2017 13:35:55 +0100
Subject: [PATCH] Ext png for virtualization-job-workflow
---
docs.it4i/anselm/software/virtualization.md | 2 +-
...job-workflow => virtualization-job-workflow.png} | Bin
2 files changed, 1 insertion(+), 1 deletion(-)
rename docs.it4i/img/{virtualization-job-workflow => virtualization-job-workflow.png} (100%)
diff --git a/docs.it4i/anselm/software/virtualization.md b/docs.it4i/anselm/software/virtualization.md
index 668a12ee7..a5c7c95aa 100644
--- a/docs.it4i/anselm/software/virtualization.md
+++ b/docs.it4i/anselm/software/virtualization.md
@@ -47,7 +47,7 @@ IT4Innovations does not provide any licenses for operating systems and software
We propose this job workflow:
-
+
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.
diff --git a/docs.it4i/img/virtualization-job-workflow b/docs.it4i/img/virtualization-job-workflow.png
similarity index 100%
rename from docs.it4i/img/virtualization-job-workflow
rename to docs.it4i/img/virtualization-job-workflow.png
--
GitLab