[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=39&rev2=40

  #pragma keywords BOINC, Grid Computing, Volunteer Computing, Open Source, Debian
  #pragma description Tutorial for preparing a Debian-based server instance for a BOINC project.
  
+ '' THESE PAGES ARE STILL UNDER DEVELOPMENT ''
+ 
  This tutorial will help you create BOINC project with Debian server without using virtual images provide from BOINC. See [[BOINC/Server]] for an overview on BOINC-Server with Debian related issues. For an overview and guide on how to compile the BOINC package from the pkg-boinc git repository, see [[BOINC/Development/GitUsage]].
  
  <<TableOfContents(2)>>
@@ -12, +14 @@

  To see more info about how to install and config BOINC server, please look at [[http://boinc.berkeley.edu/trac/wiki/ProjectMain|BOINC project wiki]] and 
  the "See also" section on this page.
  
+ = Preparations =
+ 
+ The BOINC server as compiled from the BOINC sources does not perform directly. That BOINC server is "only" the skeleton for the real server. For that reason, the Debian package is named no longer "boinc-server" but now presents itself as "boinc-server-maker".
+ 
+ In the following, please distinguish 
+  1. the folder to which the files of the BOINC server templates install ('/usr/share/boinc-server')
+  1. the name of the Debian package providing those files ('boinc-server-maker')
+  1. the location of your very own project ('you/name/it')
+ 
+ The preparation from the Debian sources is not too different from a preparation from
+ the original source tree. Debian should just shorten the process to a first success.
+ 
- = Install BOINC Server =
+ == Install BOINC Server ==
  
+ 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.
+ 
- == Installation according to the books - without the Debian server package ==
+ === Installation according to the books - without the Debian server package ===
  
   1. Install BOINC server dependencies : {{{ 
  sudo apt-get install subversion build-essential apache2 php5 mysql-server php5-gd php5-cli php5-mysql python-mysqldb libtool automake autoconf pkg-config libmysql++-dev libssl-dev
@@ -33, +50 @@

  make
  }}}
  
- == Installation with the Debian server package ==
+ === Installation with the Debian server package ===
  
-  1. Install boinc-server package from unstable : {{{
+  1. Install boinc-server-maker package from unstable : {{{
- sudo apt-get install boinc-server
+ sudo apt-get install boinc-server-maker
  }}}
-  2. --(Add www-data user to boincadm group : {{{sudo adduser www-data boincadm}}} )-- 
-  next upload will perform this in the postinst
  
- = Project-specific configuration =
+ == Project-specific configuration ==
  
- The project-specific bits should probably better be project-specific, indeed. One would then need a Debian package for every project. One such could be prepared for every example provided with the BOINC source tree.
+ The preparation of the final project from the BOINC server template is a manual process. That should be applied only once for every project and then for updates of the BOINC server sources. One could (in principle) prepare Debian packages for such project specific configurations. The [[DebPkg:boinc-server-maker]] package described on this page would then become a build dependency for the project. This is likely to happen but has not yet been addressed. 
  
- This has not yet been addressed. 
- 
- == Create and config BOINC project ==
+ === Create and config BOINC project ===
+ 
+ The BOINC server as compiled from the BOINC sources does not perform directly.
  
  The following needs to be performed for every project, with or without the Debian BOINC server package. In the following we will work on a single BASH shell. This allows us to use mostly self-explanatory variables to help your local adaptation.
  
- === Secret words ===
+ ==== Secret words ====
  
  Please define the password to be used to receive write access to your BOINC database. And also specify the name of the project.
  {{{
@@ -59, +74 @@

  dbprojectname=boinctest
  }}}
  
- === Create MySQL database for BOINC project ===
+ ==== Create MySQL database for BOINC project ====
  
  With the variables defined before, you can just copy and pasted the code below: {{{
  if ! echo "DROP USER 'boincadm'@'localhost'" | mysql -u root -p; then
@@ -136, +151 @@

  sudo a2ensite  ${fileprojectname}.httpd.conf 
  sudo /etc/init.d/apache2 reload
  }}}
+ 
+ === Test web interface ===
+ 
+ The web site should now be accessible. It should be available as an alias "$fileprojectname", please look it up in "/etc/apache2/sites-enabled/${filesprojectname}.httpd.conf". You will find the automated home page to need some further manual adjustments - which does not really encourage to update the server version too frequently, we presume.
+ 
+ If the home page does not show up then there may be some missing file or some bogus file permission. The inspection of "/var/log/apache/error.log" should bring sufficient insights
+ to fix the issue.
+ 
+ = Add functionality =
  
  == Configure and start BOINC demons ==
  
@@ -170, +194 @@

  root      4555  0.0  0.2  27336  2240 ?        S    10:33   0:00 file_deleter -d 3
  }}} Something lets me think that those processes should better run as "boincadm" than via 'sudo', but, well, let's be happy for now.
  
- == Test web interface ==
- 
- The web site should now be accessible. It should be available as an alias "$fileprojectname", please look it up in "/etc/apache2/sites-enabled/${filesprojectname}.httpd.conf". You will find the automated home page to need some further manual adjustments - which does not really encourage to update the server version too frequently, we presume.
- 
- If the home page does not show up then there may be some missing file or some bogus file permission. The inspection of "/var/log/apache/error.log" should bring sufficient insights
- to fix the issue.
- 
  == Add your own application ==
  
  The only thing that counts to have is the application that helps your very personal task at hand. This will be addressed in the upcoming section. The section at hand will take one of the example projects.
@@ -219, +236 @@

  = Why to use (or not to use) the Debian BOINC server package =
  
  The concept of the BOINC server package is slightly irritating in that it itself is not a working server but something from which a server infrastructure is generated. It provides all the binaries and header files for local developments and thus saves some considerable time to prepare such and ensures to have all the libraries in place that the community has determined to be of help.
+ 
+ The typical advantages of Debian do apply. It should for instance be possible, to change the server architecture
+ at any time from one platform to another. If it is running on your laptop, it should e.g. also run on an ARM netplug.
  
  The package is still too experimental to use in a production environment. But, hey, we will be getting there over time.