Input file handling

BOINC offers three paradigms for handling job input files.

Local model

In this paradigm (typically used with local job submission) input files exist on the server prior to job submission. The programs or scripts that create jobs copy or move them to the download hierarchy, typically using stage_file.

Files are deleted automatically after jobs are completed.

This model assumes each file is used by a single job; otherwise a file could be deleted while still in use by a second job.

Remote input file management

In this model, input files are uploaded to the BOINC server via web RPCs. Files can be used by multiple jobs. This model is used with batch-oriented remote job submission. It uses two database tables:

• job_file: describes an input file; keeps track of what files are on the server.
• job_batch_assoc: links a batch to an input file; a file is deleted only when all batches linked to it are retired.

Details are here.

User file sandbox

In this model, job submitters can upload and manage files on the server, via a web interface. This is used for BUDA and other web-based job submission systems. Eliminates the need to think about immutability.

Details are here.