Changes between Version 2 and Version 3 of MultiUser


Ignore:
Timestamp:
Jul 25, 2011, 12:37:04 AM (13 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MultiUser

    v2 v3  
    33This document describes a set of BOINC server features
    44that support projects with multiple users (i.e., job submitters).
    5 An example is science portals such as NanoHUB.org.
     5A user may represent a single scientist, a research group, or some other organizational entity,
     6An example of a multi-user project is a science portal such as NanoHUB.org.
    67
    7 The features support the following goals:
     8Such projects are typically structured so that users interact with the project through a web-based interface,
     9possibly served on a computer other than the BOINC server.
     10The BOINC server is accessible only to '''administrators'''.
     11
     12BOINC's design supports the following goals:
    813
    914 * The set of users may be large (1000s) and dynamic.
     
    1217 * Users have privacy: a user cannot see the computational results of other users.
    1318 * The access rights of a user (e.g., the applications to which they can submit jobs)
    14    can be limited.
    15 
    16 Projects using these features would typically have the following structure:
    17 
    18  * Users interact with the project through a web-based interface,
    19    possibly served on a computer other than the BOINC server.
    20  * The BOINC server is accessible only to '''administrators'''.
     19   can be limited by project administrators.
    2120
    2221== User identity ==
     
    2625and this may affect their quota (see below).
    2726
    28 
    2927== Access control ==
    3028
    3129To submit jobs, users must be given access by administrators.
    32 This is done via the project admin web interface.
     30This can done via the project admin web interface.
    3331Users may be given permission to submit jobs only to specific applications,
    3432or to submit jobs to any current or future applications.
     
    5553   e.g. by participating in the message boards.
    5654
    57 Quotas are set by administrators, via the admin web interface
    58 or other mechanism.
     55Quotas are set by administrators, via the admin web interface or other mechanism.
     56
     57== Implementation notes ==
     58
     59Two new DB tables support the multi-user features
     60
     61 * '''user_submit''': access control and quota info for a user
     62 * '''user_submit_app''':  per (user, app) access control info.