|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| == Summary ==
| |
|
| |
|
| Yerba is the job execution engine used by CoGe. For more details on why the job engine is used by CoGe refer to [http://genomevolution.org/wiki/index.php/JEX Job Execution Framework].
| |
|
| |
| == Installation ==
| |
|
| |
| For installation instructions please refer to the [https://github.com/LyonsLab/Yerba/tree/temp git repository] or the README.md in the repository.<br>
| |
|
| |
| To clone the repository run the command:
| |
|
| |
| git clone https://github.com/LyonsLab/Yerba.git
| |
|
| |
| == Usage<br> ==
| |
|
| |
| Yerba has two components the job daemon ''yerbad'' and the command line client ''yerba''. The job daemon is started started when the server is first booted. Additionally, cctool's catalog and worker pool need to be running. ''yerba' is a command line interface to the job engine to check the status of the job engine. More features are planned in the future.
| |
|
| |
| ==== yerbad<br> ====
| |
|
| |
| To (manually) start the job engine you need to start each script.
| |
|
| |
| sudo start catalog_server
| |
| sudo start work_queue_pool
| |
| sudo start yerba
| |
|
| |
| ==== yerba ====
| |
|
| |
| This command currently only checks for a response from the job engine.
| |
| $YERBA_DIR/bin/yerba
| |
|
| |
| Another method to check the status of the job engine is:
| |
| sudo status yerba
| |
|
| |
| == CoGe yerba utilities<br> ==
| |
| CoGe has several utilities that provide functionality beyond the scope of the job engine.
| |
|
| |
| ==== update_jobs ====
| |
| This script keeps the CoGe jobs table up to date. By default the command will perform a dry run and not update the database.
| |
| coge/scripts/update-jobs coge.conf
| |
|
| |
| To update the database the command can then be ran with the update argument.
| |
| coge/scripts/update-jobs coge.conf --update
| |