| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| start [2016/02/24 21:43] – [OAR Uses and Users] neyron | start [2016/02/24 21:48] – neyron |
|---|
| ===== Overview ===== | ===== Overview ===== |
| |
| This batch system is based on a database (PostgreSQL (preferred) or MySQL), a script language (Perl) and an optional scalable administrative tool (e.g. [[http://taktuk.gforge.inria.fr|Taktuk]]). It is composed of modules which interact mainly via the database and are executed as independent programs. Therefore, formally, there is no API, the system interaction is completely defined by the database schema. This approach eases the development of specific modules. Indeed, each module (such as schedulers) may be developed in any language having a database access library. | OAR architecture is based on a database (PostgreSQL (preferred) or MySQL), a script language (Perl) and an optional scalable administrative tool (e.g. [[http://taktuk.gforge.inria.fr|Taktuk]]). It is composed of modules which interact mainly via the database and are executed as independent programs. Therefore, formally, there is no API, the system interaction is completely defined by the database schema. This approach eases the development of specific modules. Indeed, each module (such as schedulers) may be developed in any language having a database access library. |
| |
| ===== Main features ===== | ===== Main features ===== |
| |
| ===== Why using OAR ===== | ===== Why using OAR ===== |
| ==== OAR advantages ==== | |
| |
| We present below some points that explain benefits of the new version of OAR. | |
| |
| === A better resource management === | === A better resource management === |
| |
| |
| ===== OAR capabilities ===== | ===== More technical details ===== |
| |
| Oar is an opensource batch scheduler which provides a simple and flexible exploitation of a cluster. | Oar is an opensource batch scheduler which provides a simple and flexible exploitation of a cluster. |
| |
| It manages resources of clusters as a traditional batch scheduler (as PBS / Torque / LSF / SGE). In other words, it doesn't execute your job on the resources but manages them (reservation, acces granting) in order to allow you to connect these resources and use them. | It manages resources of clusters like other traditional batch scheduler (as PBS / Torque / LSF / SGE). In other words, it doesn't execute your job on the resources but manages them (reservation, acces granting) in order to allow you to connect these resources and use them. |
| |
| Its design is based on high level tools: | Its design is based on high level tools: |
| * scalable exploiting tool Taktuk. | * scalable exploiting tool Taktuk. |
| |
| It is flexible enough to be suitable for production clusters and research experiments. It currently manages over than 5000 nodes and has executed more than 5 million jobs. | It is flexible enough to be suitable to manage production HPC clusters as well as other computer infrastructures such as research testbeds like [[http://www.grid5000.fr|Grid'5000]]. |
| |
| OAR advantages: | OAR advantages: |
