Difference between revisions of "Yerba"
From CoGepedia
| Line 1: | Line 1: | ||
== Summary == | == Summary == | ||
| − | Yerba is the job execution engine used by CoGe. For more details on how the job engine is used by CoGe refer to [http://genomevolution.org/wiki/index.php/JEX Job Execution Framework]. | + | Yerba is the job execution engine used by CoGe. For more details on how the job engine is used by CoGe refer to [http://genomevolution.org/wiki/index.php/JEX Job Execution Framework]. |
<span style="font-size: 20px; line-height: 1.5em;">Installation</span> | <span style="font-size: 20px; line-height: 1.5em;">Installation</span> | ||
| Line 9: | Line 9: | ||
== Usage<br> == | == 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, the work_queue catalog and worker pool need to be started as well. The command line client is used to check the status of the job engine. | |
==== yerbad<br> ==== | ==== yerbad<br> ==== | ||
==== yerba ==== | ==== yerba ==== | ||
Revision as of 18:01, 30 September 2013
Contents
Summary
Yerba is the job execution engine used by CoGe. For more details on how the job engine is used by CoGe refer to Job Execution Framework.
Installation
For installation instructions please refer to the github repository
Usage
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, the work_queue catalog and worker pool need to be started as well. The command line client is used to check the status of the job engine.
