Changes between Version 7 and Version 8 of RemoteOverview


Ignore:
Timestamp:
01/30/17 14:48:08 (11 months ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RemoteOverview

    v7 v8  
    22= Remote job submission =
    33
    4 "Remote job submissions" means that jobs are submitted
    5 by scripts or programs running on hosts other than the BOINC server.
     4"Remote job submission" means that jobs are submitted
     5by scripts or programs running outside the BOINC server;
     6they need not have login access to the BOINC server.
     7The scripts use [RemoteJobs Web RPCs] to create batches and jobs, and to manage input and output files.
    68
    7 BOINC provides components that can be used to build such systems.
    8 We'll list some example systems, then describe the components.
     9Remote job submission differs from local submission in several ways:
     10
     11 * A job submitters must have a user account on the BOINC project.
     12   Their submissions are associated with that account, and must supply its credentials.
     13   Users must be granted [MultiUser access rights and quotas] in order to create jobs.
     14 * Jobs are submitted and controlled in "batches".
     15   If you want to submit a single job, submit a batch with one element.
     16 * Don't use an assimilator for remote jobs;
     17   Instead, use the "retire batch" operation to tell that the batch's
     18   file and database records can be cleaned up.
     19 * Job submitters can monitor and control their batches and jobs via
     20   an interface on the BOINC project web site.
    921
    1022== Example: Science portal ==
    1123
    12 Users submit jobs using forms on a web site other than the project web site:
     24Users submit jobs using forms on a web site outside the BOINC server.
    1325
    1426[[Image(submit.png)]]
    15 
    16 The scripts implementing these forms would use
    17 [RemoteJobs Web RPCs] to create batches and jobs.
    18 
    19 Input files can be handled in any of several ways:
    20 
    21  * Managing them using [RemoteInputFiles#Content-basedfilemanagement Web RPCs].
    22  * Using the [RemoteInputFiles#Per-userfilesandbox user file sandbox] mechanism.
    23  * Serving them from a remote server.
    2427
    2528== Example: Condor/BOINC bridge ==
     
    2730[[Image(condor.png)]]
    2831
    29 In such systems, users submit jobs to a Condor system
    30 using any a command-line or GUI-based interface.
    31 The Condor system may, depending on load conditions, route the job to a BOINC project.
    32 This system uses web RPCs for all functions.
    33 
    34 == Components supplied by BOINC ==
    35 
    36 === Web RPCs for input file management ===
    37 
    38 BOINC provides [RemoteInputFiles#Content-basedfilemanagement Web RPCs for remotely managing input files],
    39 and a C++ binding of this API.
    40 
    41 === Web RPCs for job submission ===
    42 
    43 BOINC provides [RemoteJobs Web RPCs for creating and managing jobs].
    44 
    45 === Per-user file sandbox ===
    46 
    47 BOINC provides [RemoteInputFiles#Per-userfilesandbox a web-based system allowing users to remotely manage input files].
     32Users submit jobs to a Condor system using a command-line or GUI-based interface.
     33The Condor system routes the job to a BOINC project.
     34Details are [CondorBoinc here].