From d8fc953fcfd576049881a3b2f508ed3ff0830cca Mon Sep 17 00:00:00 2001 From: Martin Polanka Date: Fri, 22 Jul 2016 23:06:38 +0200 Subject: [PATCH] Updated Submissions flow (markdown) --- Submissions-flow.md | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/Submissions-flow.md b/Submissions-flow.md index e03a027..e2c3883 100644 --- a/Submissions-flow.md +++ b/Submissions-flow.md @@ -33,13 +33,18 @@ Broker gets information about new submission from web application. At this point Worker gets request from broker to evaluate particular submission. Next step is to evaluate given submission and results upload to fileserver. After this worker only send broker that submission was evaluated. More detailed description follows: -- T -- O -- D -- O -- . -- . -- . +- "listening" thread gets multipart message from broker with command "eval" +- "listening" thread hand over whole message through inproc socket to "execution" thread +- "execution" thread now has to prepare all things and get ready for execution +- temporary folders are initated (but not created) this includes folder with source files, folder with downloaded submission, temporary directory for all possible types of files and folder which will contain results from execution +- if some of the above stated folders is already existing, then it's deleted +- after successfull initiation submission archive is downloaded to newly created folder +- submission archive is decompressed into submission files folder +- all files from decompressed archive are copied into evaluation directory which can be used for execution in sandboxes +- all other folders which were not created are created just now +- it's time to build job from configuration +- job configuration file is located in evaluation directory if exists +- ... ## Broker