| | 1 | = Assigned work = |
| | 2 | |
| | 3 | This mechanism serves two purposes: |
| | 4 | |
| | 5 | * 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, to test CPUs, etc. |
| | 7 | |
| | 8 | A host with assigned jobs won't get sent any other jobs until the assigned ones are reported. |
| | 9 | |
| | 10 | Assigned jobs are not validated or assimilated. |
| | 11 | You must develop your own scripts or programs to process and clean up finished jobs. |
| | 12 | |
| | 13 | To enable this feature you must add |
| | 14 | {{{ |
| | 15 | <enable_assigned_work>1</enable_assigned_work> |
| | 16 | }}} |
| | 17 | to your config.xml file. |
| | 18 | |
| | 19 | == Creating assigned work == |
| | 20 | |
| | 21 | The [WorkGeneration '''create_work''' script and function] |
| | 22 | take an optional '''host_id''' argument. |
| | 23 | If -1 it means send the job to all hosts. |
| | 24 | If positive it means send the job to the host with that ID. |
| | 25 | |
| | 26 | The names of workunits for assigned jobs must include '''asgw'''. |
| | 27 | |