[Debian Wiki] Update of "BOINC/ServerGuide" by SteffenMoeller

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "BOINC/ServerGuide" page has been changed by SteffenMoeller:
http://wiki.debian.org/BOINC/ServerGuide?action=diff&rev1=126&rev2=127

  #pragma keywords BOINC, Grid Computing, Volunteer Computing, Open Source, Debian
  #pragma description Tutorial for preparing a Debian-based server instance for a BOINC project.
  
- = Intro =
+ = Tutorial on Setting up a BOINC Project =
  
- This page is a tutorial for the setup of a BOINC project on the basis of the ''boinc-server-maker'' package. It is currently (12/2012) being updated and that recent version of the boinc-server-maker package is not yet publicly availalble. Also, the tutorial is not consistent in the amount of insights in Linux that is required from the reader. At some point, it should understood by anyone with sincere interest in computing and sufficient time to follow things up.
+ This page is a tutorial for the setup of a BOINC project on the basis of the ''boinc-server-maker'' package soon to ship with Debian and Ubuntu. It is currently (12/2012) being updated and that recent version of the boinc-server-maker package is not yet publicly availalble. Contact us about it. Also, the tutorial is not consistent in the amount of insights in Linux that is required from the reader. Some obvious-to-many bits are explained, some less obvious pointers may not be given. At some point, it should be understood by anyone with sincere interest in computing and sufficient time to follow things up. Feedback helps.
  
  {{http://boinc.berkeley.edu/logo/www_logo.gif||align="right"}}
  <<TableOfContents(2)>>
  
- = Preparations =
+ == Overview ==
  
- == Environment ==
+ The path towards a complete BOINC project we see four major components.
+  1. With the project initialisation, the basis of everything, comes the setup of the web pages.
+  1. The web page is contacted by clients of the volunteers asking for applications to run. Those need to be set up for many platforms, like 32 and 64 bit environments, Windows, Mac and Linux, whatever the volunteer's community is equipped with and the software is available for.
+  1. Work units that are shipped to the clients to make up compute tasks need to be created. This is not required to happen in one go. It is OK (some may say preferable, this depends on the problem) to have the generation of later workunits depend on the results sent back for the early ones.
+  1. Validation and archiving of results.
  
+ This tutorial supports an order like the above. This introduction works closely with what the BOINC developers already provide and as such also use their example projects. Its ends with a complete BOINC project and the reader will know what parts to substitute for its own project.
+ 
- === Hardware: disk space and internet connection ===
+ == What you need: disk space and internet connection ==
  
- The hardware you need depends on the problem you address. When distributing many jobs, you need strong upload bandwidth, which means that with the typical asymmetric DSL connects at home this is difficult. Universities obviously will not have such a problem. In clinical or other strongly firewalled setups find an external hoster or a collaborating non-clinical institute. You may also decide to use the [[Cloud]]. A regular 32 bit machine is likely to be sufficient, if that machine can concentrate on distributing the job and does not need too much of work for post-processing of results.
+ The hardware you need depends on the problem you address. When distributing many jobs, you need strong upload bandwidth, which means that with the typical asymmetric DSL connects at home this is difficult. Universities obviously will not have such a problem. In clinical or other strongly firewalled setups find an external hoster or a collaborating non-clinical institute with a demilitarised zone. You may also decide to use the [[Cloud]] or just rent some external machine. A regular 32 bit machine is likely to be sufficient if that machine can concentrate on distributing the job and does not need too much of work for post-processing of results.
  
+ To just learn and get started, and fix bugs of this tutorial, just use what you have. If on a non-Debian machine, consider running a virtual machine with 512MB memory and 10 GB of disk sapce, leaving some room for many binaries and work units / results.
+ 
+ ||                                  ||                 ||                     ||                 ||
+ ||[[BOINC/ServerGuide/Initialisation|Project and Website Initialisation]]||[[BOINC/ServerGuide/ApplicationSetup|Application Setup]]||[[BOINC/ServerGuide/WorkUnitGeneration|Work Unit Generation]]||[[BOINC/ServerGuide/ResultManagement|Result Management]]||
+ 
+ 
+ = The Website =
+ 
- === Software: BOINC Server Template files  ===
+ == Software: BOINC Server Template files  ==
  
  This section first explains the installation of the BOINC server template sources
  from the source tree and then the same for those using the Debian boinc-server-maker package.
@@ -301, +315 @@

  }}}
  or the 'ops/create_forums.php' file be found in the browser.
  
- The user interface is - from a technical point of view - now set. It remains the application side to be configured. With Debian we can help again. The tasks are:
+ The user interface is - from a technical point of view - now set. It remains the application side to be configured.
-  * set up binaries for applications to be run by the volunteers
-  * produce work for those applications
-  * validate the and archive the results
  
  = Add functionality =