Configure web server to submit jobs » History » Version 1
Neil Voss, 05/19/2010 02:12 PM
1 | 1 | Neil Voss | h1. Configure web server to submit jobs |
---|---|---|---|
2 | |||
3 | h2. Remote Appion Processing through ssh |
||
4 | |||
5 | A more advanced way to run appion script is done through an ssh session. This is equivalent of having you ssh into a computer and starting the appion processes. |
||
6 | |||
7 | There are two kinds of appion processes: |
||
8 | * The first is a single-node process that can be run on a stand-alone workstation or the head-node of a computer cluster without PBS. |
||
9 | * The second is a multiple-node process that requires PBS to run on the cluster. |
||
10 | |||
11 | When you use "Just Show Command" option, it is always a single-node process, but if you run through ssh it could be either, depending on the demand of the process. For example, imageuploader.py is typically always run as single-node process while maxlikeAlignment.py is either run on single-node with "Just Show Command" or as a PBS job submission when you run through ssh. |
||
12 | |||
13 | h2. Install the php-ssh2 extension |
||
14 | |||
15 | bq. For newer systems the extension is available through the repository, e.g., on Fedora 12 type "@sudo yum install php-pecl-ssh2@" |
||
16 | |||
17 | This enables an ssh session initialized from appionweb |
||
18 | # Download and install the ssh2 extension for php as instructed at its download site: |
||
19 | * http://www.php.net/manual/en/ssh2.installation.php |
||
20 | Install openssl and compile libssh first before compiling php-ssh2 extension. Once you get the final ssh2.so, add it in your php.ini |
||
21 | |||
22 | The extension module is added to php in the same way as does the php-mrc module we distribute for the viewing mrc images through php. To check whether it worked and for alternative way to make php recognize the module used in newer php, see http://emg.nysbc.org/documentation/leginon/bk02ch04s07.php under the section *Check php information* and *Alternative approach if mrc module does not show up in info.php output* |
||
23 | |||
24 | h2. configuration at web server side |
||
25 | |||
26 | *IMPORTANT*: What we refer here as _your_cluster.php_ should not be taken literally. For example, if you access your cluster through network with a name "bestclusterever", you should name your cluster configuration php file *bestclusterever.php*, not _your_cluster.php_. |
||
27 | # Go to your_dbem_1_5_1/processing directory |
||
28 | # Copy *default_cluster.php* to _your_cluster.php_ |
||
29 | # [[ClusterPhpSettings|Edit your_cluster.php]] to correspond to your cluster configuration. |
||
30 | # Edit *config_processing.php* to add your cluster and, if desired, a stand-alone workstation as processing_host and register the _your_cluster.php_ you just created. |
||
31 | |||
32 | <pre> |
||
33 | $PROCESSING_HOSTS[]="your_stand-alone_processing_workstation"; |
||
34 | $PROCESSING_HOSTS[]="your_cluster"; |
||
35 | $CLUSTER_CONFIGS= array ( |
||
36 | 'your_cluster' |
||
37 | ); |
||
38 | </pre> |