Changes between Version 3 and Version 4 of AssignedWork


Ignore:
Timestamp:
Feb 16, 2008, 5:59:19 AM (17 years ago)
Author:
Ageless
Comment:

fixing typos

Legend:

Unmodified
Added
Removed
Modified

  • AssignedWork

    v3 v4  
    44
    55 * To assign a particular job to a particular host.
    6  * To assign a particular job to be done on ALL hosts for which an app version exists.  This could be used to run application-specific benchmarks, test for hardware or softwar features, or test CPUs.
     6 * To assign a particular job to be done on ALL hosts for which an app version exists.  This could be used to run application-specific benchmarks, test for hardware or software features, or test CPUs.
    77
    88A host with assigned jobs won't get any other jobs until the assigned ones are finished and reported.
    … …  
    2424If positive it means assign the job to the host with that ID.
    2525
    26 The names of workunits for assigned jobs must include the string '''asgw'''
     26The names of work units for assigned jobs must include the string '''asgw'''
    2727(this prevents them from being validated or assimilated).
    2828
    … …  
    3535== Implementation ==
    3636
    37 Results for assigned workunits are created on demand (in the scheduler) rather than by the transitioner.
     37Results for assigned work units are created on demand (in the scheduler) rather than by the transitioner.
    3838
    3939Assignments are stored in an '''assignments''' table.
    4040Each record contains a host ID (or -1) and a WU ID.
    4141
    42 If <enable_assigment> is set in the config file,
     42If <enable_assignment> is set in the config file,
    4343the scheduler checks for assignment records for the given host.
    4444If it finds any for which the result has not already been reported