Broadcast and targeted jobs

BOINC has two mechanisms that let you control what hosts a job runs on: Broadcast jobs and Targeted jobs.

Broadcast jobs

This mechanism lets you assign a job to all hosts, both current and future (or to all hosts belonging to a particular user or a particular team).

This could be used to run application-specific benchmarks, or to test for hardware or software features.

Broadcast jobs are executed exactly once on a given host. It the job fails for any reason, it is not retried. Broadcast jobs are not handled by a [ValidateIntro? validator[ or assimilator. You must develop your own daemon that processes completed broadcast jobs.

To enable broadcast jobs you must add

<enable_assignment_multi>1</enable_assignment_multi>

to your config.xml file.

To create a broadcast job, run the create_work script with one of following optional arguments:

--assign_multi

assign the job to all hosts

--assign_user_multi ID

assign the job to all hosts of the given user

--assign_team_multi ID

assign the job to all hosts of the given team

After creating a broadcast job, you must either

• stop and start the project, or
• touch the file reread_db in the project directory

The assign.php script (in ops/) lets you manage broadcast jobs. It shows a list of broadcast jobs and their status, and lets you remove broadcast jobs.

Targeted jobs

Targeted jobs are like regular jobs except that they are restricted to run on either

• a particular host
• hosts belonging to a particular user
• hosts belonging to a particular team

For example, suppose your project has a group of dedicated hosts such as a cluster or a set of cloud nodes. You can run the BOINC client on those hosts, attached to a particular user account. Then, if you target a job at that user, it will run only on the dedicated hosts.

Targeted jobs are validated and assimilated like other jobs. They are not replicated; if the job fails on one host in the set, it will be retried on another host in the set, and so on until it completes.

There are two ways to create targeted jobs. The first is create a job that is targeted from the beginning. To do this, run the create_work script with one of following optional arguments:

--assign_host ID

assign the job to the given host

--assign_user ID

assign the job to one host of the given user

--assign_team ID

assign the job to one host of the given team

The second way is to transform an existing job into a targeted job. This might be done, for example, as part of a system that accelerates the completion of batches of jobs by sending the "stragglers" to dedicated hosts.

Currently the only way to do this is via a C++ API call, and you can only target the job to a user. The call is:

int restrict_wu_to_user(DB_WORKUNIT& wu, int userid);