What is a BOINC Powered Project?

From Unofficial BOINC Wiki

Jump to: navigation, search

Contents

[edit] General

A BOINC Powered Project consists of the following components:

Multiple BOINC Powered Projects can exist on the same Host. This can be handy for creating separate Projects for testing and debugging.

The easiest way to create a Project is with the Make Project Script, which creates skeletal versions of the above components.

A BOINC Powered Project must be stopped when maintenance activities (e.g. changing the configuration file or database) are being performed. This is done Using Project Control Scripts.

[edit] The Project Master URL

Each BOINC Powered Project is publicly identified by a Project Master URL. The Project's Master Page at this URL has two functions.

<scheduler>http://host.domain.edu/cgi/scheduler</scheduler>
<scheduler>http://host2.domain.edu/cgi/scheduler</scheduler>
that give the URLs of the project's Scheduling Servers. These tags should be embedded within HTML comments. The BOINC Daemon reads and parses the Project's Master Page to locate Scheduling Servers. If at any point it is unable to connect to any Scheduling Server for a specific BOINC Powered Project, it rereads the Project's Master Page. This mechanism lets a Project move or add Scheduling Servers.

The Make Project Script creates a Master Page in the directory project/html/user/index.php. This file includes the file 'schedulers.txt', which contains the list of <scheduler>elements.

[edit] UCB Source

[edit] Copyright ©

  • 2005 University of California
  • 2005 Paul D. Buck

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.

Personal tools