{"id":336,"date":"2015-03-30T00:31:27","date_gmt":"2015-03-29T23:31:27","guid":{"rendered":"http:\/\/graal.ens-lyon.fr\/~diet\/?page_id=336"},"modified":"2015-04-27T21:04:25","modified_gmt":"2015-04-27T20:04:25","slug":"lrms","status":"publish","type":"page","link":"https:\/\/graal.ens-lyon.fr\/diet\/?page_id=336","title":{"rendered":"LRMS (Batch Scheduler)"},"content":{"rendered":"

LRMS DIET Management<\/h1>\n
\n
<\/a><\/p>\n
\"Draw<\/a>

Draw Gantt example<\/p><\/div>\n<\/div>\n

\n

Overview of LRMS (Local Ressource Management System)<\/h2>\n

Parallel resources are generally accessible through reservation systems, also called batch systems. To execute their jobs, clients have to submit via special mnemonics and chosen options a script that contains the command line that launches the job. Options are not necessarily given in the submission line, but can also appear in the script with a correct syntax. Several batch systems exist. Among them, one can cite Loadleveler<\/a><\/span> on IBM resources, OpenPBS<\/a><\/span> or Torque<\/a><\/span> , which are forks of the well-know PBS system, and OAR<\/a><\/span> developped by IMAG<\/a><\/span> at Grenoble, and used in the Grid’5000<\/a><\/span> Project of a research grid. Most of the submitted jobs are parallel jobs, coded from the MPI<\/a><\/span> standard with an instantiation like MPICH<\/a><\/span> or LAM<\/a><\/span>.<\/p>\n

In order to correctly use a batch system, a client must provide in the submission line or in the script several information like: the number of machines to assign, the duration that they will be used, the number of MPI processes to use (indeed, most applications still use MPI-1.2 implementations where the number of processes is statically defined at the spawning of the jobs).<\/p>\n

<\/h2>\n

Problematic<\/h2>\n

The Grid will only be used if its resources can be made easily available to clients. Grid middlewares are a good means to propose this transparent access, but few of them have the possibility to submit transparently for the user to batch systems, i.e., with the same manner than with sequential jobs: only the service and its input parameters are provided by clients. Information like the walltime, the number of machines and processes, must be determined by the middleware when choosing the parallel resources on which to submit in its scheduling phase.<\/p>\n

 <\/p>\n

Interfacing DIET with LRMS<\/h2>\n

We have firsly considered Elagi. This library allows to remotely submit on batch systems. But in our case, a DIET server (SeD) is deployed on each computing resource. So, it is locally present with the batch system. Then, most of the possibilities of Elagi are not used.<\/p>\n

We are actually extending the DIET server API such that any parallel application can be called from a SeD without further client information.<\/p>\n

 <\/p>\n

Performance prediction and scheduling algorithms<\/h2>\n

Simbatch<\/a><\/span> is a module of the grid simulator Simgrid<\/a><\/span>. It has been designed and developed to model batch systems in order to test realisticly distributed scheduling algorithms, and provide good performance prediction functions that can be embedded in the SeD.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

LRMS DIET Management Overview of LRMS (Local Ressource Management System) Parallel resources are generally accessible through reservation systems, also called batch systems. To execute their jobs, clients have to submit via special mnemonics and chosen options a script that contains the command line that launches the job. Options are not necessarily given in the submission […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":79,"menu_order":5,"comment_status":"closed","ping_status":"open","template":"","meta":{"footnotes":""},"class_list":["post-336","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=\/wp\/v2\/pages\/336","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=336"}],"version-history":[{"count":3,"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=\/wp\/v2\/pages\/336\/revisions"}],"predecessor-version":[{"id":380,"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=\/wp\/v2\/pages\/336\/revisions\/380"}],"up":[{"embeddable":true,"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=\/wp\/v2\/pages\/79"}],"wp:attachment":[{"href":"https:\/\/graal.ens-lyon.fr\/diet\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=336"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}