From c9839e957af3f15b942f7ab13871e0060f12986e Mon Sep 17 00:00:00 2001 From: Teyras Date: Tue, 10 Jan 2017 21:58:12 +0100 Subject: [PATCH 1/2] a bit about file uploads --- Rewritten-docs.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Rewritten-docs.md b/Rewritten-docs.md index 44c347f..510cad5 100644 --- a/Rewritten-docs.md +++ b/Rewritten-docs.md @@ -1489,6 +1489,15 @@ container implementation. @todo: what files are stored in api, why there are duplicates among api and fileserver +#### Uploading files + +There are two cases when users need to upload files using the API – submitting +solutions to an assignment and creating a new exercise. In both of these cases, +the final destination of the files is the fileserver. + +However, the fileserver is not publicly accessible, so the files have to be +uploaded through the API. + @todo: groups and hierarchy, describe arbitrary nesting which should be possible within instance and how it is implemented and how it could be implemented (describe only implementation if it is something what to say) From 9d156e9a827dff4e55d03375808f781d01793e02 Mon Sep 17 00:00:00 2001 From: Martin Polanka Date: Tue, 10 Jan 2017 22:50:14 +0100 Subject: [PATCH 2/2] Backend state in API --- Rewritten-docs.md | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/Rewritten-docs.md b/Rewritten-docs.md index 510cad5..509942f 100644 --- a/Rewritten-docs.md +++ b/Rewritten-docs.md @@ -1540,8 +1540,25 @@ enough to implement in low-level backend components. That also means this feature is visible and can be exploited but from our points of view it seems as appropriate compromise in simplicity. -@todo: where is stored which workers can be used by supervisors and which runtimes are available, describe possibilities and why is not implemented automatic solution - +Next thing relating backend management is storing its current state. This namely +concerns which workers are available for processing with what hardware and which +languages can be used in exercises. Another step is overall backend state like +how many jobs were processed on some particular worker, workload of broker and +workers, etc. The easiest solution is to manage these information by hand, every +instance of API has to have administrator which would have to fill them. This of +course includes only currently available workers and runtime environments, +backend statistics cannot be provided this way. + +Better solution is to let these information update automatically. This can be +done two ways either it can be provided by backend on-demand if API needs them +or backend will send these information periodically to API. Things like +currently available workers or environments are better to be really up-to-date +so this can provided on-demand if needed. Backend statistics are not necessary +stuff which can be updated periodically. But it really depends on the period of +updates, if it is short enough then even available workers, etc. could be +updated this way and be quite up-to-date. However due to lack of time automatic +refreshing of backend state will not be implemented in early versions but might +be implemented in next releases. ### Web-app