Changes between Version 2 and Version 3 of MultiHost


Ignore:
Timestamp:
Apr 27, 2007, 2:50:51 PM (17 years ago)
Author:
KSMarksPsych
Comment:

Updated links to point to wiki pages.

Legend:

Unmodified
Added
Removed
Modified

  • MultiHost

    v2 v3  
    1010
    1111== Run MySQL on a separate host ==
    12 When you initially create a BOINC project using [http://boinc.berkeley.edu/make_project.php make_project], everything runs on a single host: MySQL database server, web server, scheduling server, daemons, tasks, and file upload handler.  Of these tasks, the MySQL server does the most work (typically as much as all the others combined). So, if you need to increase the capacity of your server the first step is to move the MySQL server to a separate host (preferably a fast computer with lots of memory). Specify this host in the [http://boinc.berkeley.edu/project_options.php project configuration file].
     12When you initially create a BOINC project using [MakeProject make_project], everything runs on a single host: MySQL database server, web server, scheduling server, daemons, tasks, and file upload handler.  Of these tasks, the MySQL server does the most work (typically as much as all the others combined). So, if you need to increase the capacity of your server the first step is to move the MySQL server to a separate host (preferably a fast computer with lots of memory). Specify this host in the [ProjectOptions project configuration file].
    1313
    1414
    1515== Run server daemons and tasks on multiple hosts ==
    16 If you need more server capacity, you can move some of the server [http://boinc.berkeley.edu/project_daemons.php daemons] and [http://boinc.berkeley.edu/project_tasks.php tasks] to separate hosts. (Start by moving the one that's doing the most work).
     16If you need more server capacity, you can move some of the server [ProjectDaemons daemons] and [ProjectTasks tasks] to separate hosts. (Start by moving the one that's doing the most work).
    1717
    1818When you move daemons and tasks to other hosts, those hosts must satisfy the following rules:
    1919
    20  * The [http://boinc.berkeley.edu/groups.php project admin account] must exist on all hosts, and a user must be able to use 'ssh' to run commands on any other host without typing a password.
     20 * The [GroupPermissions project admin account] must exist on all hosts, and a user must be able to use 'ssh' to run commands on any other host without typing a password.
    2121 * The hosts must share a common network file system, and path to the project directory relative to the project admin's home directory (typically ~/projects/PROJECT_NAME) must be the same on all hosts.
    2222 * One host is designated as the project's '''main host''' in config.xml. '''The 'start', 'stop', and 'status' scripts should normally be run on the main host''' (if you run them on a different host X, they'll affect only daemons and tasks on host X).
    … …  
    2424
    2525Host locations are specified as follows:
    26  * Scheduling servers are listed in the project's [http://boinc.berkeley.edu/server_components.php master page].
    27  * The hosts on which tasks and daemons are run are specified in the [http://boinc.berkeley.edu/configuration.php config.xml] file.
    28  * Data servers are listed in [http://boinc.berkeley.edu/tools_work.php#wu_template workunit template files].
    29  * File upload handlers are listed in [http://boinc.berkeley.edu/tools_work.php#result_template result template files].
     26 * Scheduling servers are listed in the project's [ServerComponents master page].
     27 * The hosts on which tasks and daemons are run are specified in the [ProjectConfigFile config.xml] file.
     28 * Data servers are listed in [WorkGeneration template files].
     29 * File upload handlers are listed in [WorkGeneration result template files].
    3030 * Your web server runs on the host to which your project URL is mapped.
    3131
    3232
    3333== Parallelize schedulers and daemons ==
    34 If you need even more server capacity, you can parallelize most of the BOINC daemons so that multiple instances run on a single (multiprocessor) host, or on different hosts. For example, the following [http://boinc.berkeley.edu/project_daemons.php config.xml] entries run two instances of the transitioner on the host 'kosh'. Because these instances are on the same host, you must specify different output and PID files.
     34If you need even more server capacity, you can parallelize most of the BOINC daemons so that multiple instances run on a single (multiprocessor) host, or on different hosts. For example, the following [ProjectDaemons config.xml] entries run two instances of the transitioner on the host 'kosh'. Because these instances are on the same host, you must specify different output and PID files.
    3535{{{
    3636<daemon>