Changes between Version 1 and Version 2 of RemoteOverview


Ignore:
Timestamp:
Feb 15, 2013, 1:54:29 PM (11 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RemoteOverview

    v1 v2  
    1515and admins can restrict the apps for which each user is allowed to submit jobs.
    1616Users have '''quotas''' how resources are allocated to their jobs.
     17
     18== Example: single-server portal ==
     19
     20[[Image(submit2.png)]]
     21
     22Users submit jobs using forms on the project web site.
     23These forms are application-specific; you must develop them yourself.
     24Two examples are included in the BOINC distribution:
     25 * '''html/user/tree_threader.php'''
     26 * '''html/user/lammps.php'''
     27
     28TODO: the above are full of application-specific complexity;
     29provide a minimal/generic example.
     30
     31The job-submission scripts use [foo local PHP interfaces] to
     32authenticate users and to create jobs and batches.
     33
     34Input files can be handled in any of several ways:
     35
     36 * Uploading them (from the submitter's computer) as part of the submission form.
     37   The submission script would then [xxx stage them].
     38 * Using the [SubmitSandbox user file sandbox] mechanism.
     39 * Serving them from a remote server.
     40
     41== Example: multi-server portal ==
     42
     43[[Image(submit.png)]]
     44
     45In such systems, users submit jobs using forms on a web site
     46other than the project web site.
     47
     48The scripts implementing these forms would use
     49[SubmitJob Web RPCs] to create batches and jobs.
     50
     51Input files can be handled in any of several ways:
     52
     53 * Managing them using [SubmitFile Web RPCs].
     54 * Using the [SubmitSandbox user file sandbox] mechanism.
     55 * Serving them from a remote server.
     56
     57== Example: Condor/BOINC bridge ==
     58
     59[[Image(condor.png)]]
     60
     61In such systems, users submit jobs to a Condor system
     62using any a command-line or GUI-based interface.
     63The Condor system may, depending on load conditions, route the job to
     64a BOINC project.
     65This system uses web RPCs for all functions.
    1766
    1867== Components supplied by BOINC ==
     
    4392
    4493=== Web RPCs for job submission ===
    45 
    46 == Example: single-server portal ==
    47 
    48 In such systems, users submit jobs using forms on the project web site.
    49 These forms are application-specific; you must develop them yourself.
    50 Two examples are included in the BOINC distribution:
    51  * '''html/user/tree_threader.php'''
    52  * '''html/user/lammps.php'''
    53 
    54 TODO: provide a minimal/generic script.
    55 
    56 [[Image(submit2.png)]]
    57 
    58 == Example: multi-server portal ==
    59 
    60 In such systems, users submit jobs using forms on a web site
    61 other than the project web site.
    62 
    63 [[Image(submit.png)]]
    64 
    65 == Example: Condor/BOINC bridge ==
    66 
    67 In such systems, users submit jobs to a Condor system
    68 using any a command-line or GUI-based interface.
    69 The Condor system may, depending on load conditions, route the job to
    70 a BOINC project.
    71 This system uses web RPCs for all functions.
    72