Changes between Version 23 and Version 24 of RemoteJobs

Timestamp:

Nov 14, 2011, 8:49:17 PM (13 years ago)

Author:

davea

Comment:

--

RemoteJobs

@@ -19 +19 @@
 [[Image(submit.png)]]
 
-Notes:
-
- * This system is coupled with BOINC's [MultiUser multi-user project features],
-  which include access control:
-  users can submit jobs only if they have been given access by project administrators,
-  and admins can restrict the apps for which each user is allowed to submit jobs.
- * Input files must be accessible via HTTP; they are downloaded by the BOINC server
-  during job submission.
- * As jobs are completed, their output files are available to the submitting user via HTTP.
-  When a batch is complete, a zipped archive of all its output files is available
-  via HTTP.
+== Access control and quotas ==
+
+This system is coupled with BOINC's [MultiUser multi-user project features],
+which include access control:
+users can submit jobs only if they have been given access by project administrators,
+and admins can restrict the apps for which each user is allowed to submit jobs.
+Users have '''quotas''' how resources are allocated to their jobs.
+
+== Input and output files ==
+
+Input files can be supplied in any of the following ways:
+ * '''local''': the file is resident on the BOINC server, and is specified by its path.
+ * '''inline''': the file is included in the job submission request XML message.
+   It will be served to clients from BOINC server.
+ * '''semilocal''': the file is on a data server other than the BOINC server.
+   It is specified by its URL.
+   It will be downloaded by the BOINC server during job submission,
+   and served to clients from the BOINC server.
+ * '''remote''': the file is on a data server other than the BOINC server,
+   and will be served to clients from that data server.
+   It is specified by the URL, the file size, and the file MD5.
+
+As jobs are completed, their output files are available to the submitting user via HTTP.
+When a batch is complete, a zipped archive of all its output files is available via HTTP.
 
 == PHP interface ==