reserve
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
reserve [2022/09/08 18:19] – [A note on OAR job scheduling] mimbert | reserve [2022/11/18 16:43] (current) – pgirard | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Book the testbed with the Cortexlab web application ===== | ||
+ | |||
+ | **Booking the Cortexlab platform with the Cortexlab web application saves you from using the OAR commands like described in the "Book the testbed with OAR" section below.** | ||
+ | |||
+ | When logged in (https:// | ||
+ | * the planning (Drawgantt), | ||
+ | * your reservation list (of course you can delete a reservation), | ||
+ | * the button to book the testbed. | ||
+ | You can also make your reservation(s) by clicking on the "Book the testbed" | ||
+ | |||
+ | To book the testbed, you must at least : | ||
+ | * select a start date and hour, | ||
+ | * select a duration OR an end date and hour, | ||
+ | * select " | ||
+ | Then the "Book the testbed" | ||
+ | |||
+ | To go to your reservation list, just click on "My current reservations" | ||
+ | |||
===== Book the testbed with OAR ===== | ===== Book the testbed with OAR ===== | ||
Line 70: | Line 88: | ||
==== A note on OAR job scheduling ==== | ==== A note on OAR job scheduling ==== | ||
- | Be aware that OAR behaviour may sometimes be counter-intuitive: | + | Be aware that OAR behaviour may sometimes be counter-intuitive: |
* because the nodes are currently shutdown, so it needs to wake them up, which may take some time | * because the nodes are currently shutdown, so it needs to wake them up, which may take some time | ||
* because another job is running | * because another job is running | ||
- | * because the resources you ask are currently not available but oar expects them to be available in the future | + | * because the resources you ask are currently not available but OAR expects them to be available in the future |
* etc. | * etc. | ||
- | So, the only reliable way to be sure that your job is actually running is to check that the job's state is " | + | So, the only reliable way to be sure that your job is actually running is to check that the job's state is "//Running//" with command: |
< | < | ||
- | Tasks submitted to minus will never start unless the job is " | + | Tasks submitted to minus will never start unless the job is "//Running//" anyway. |
To sum-up things: | To sum-up things: | ||
- | * Submissions versus Reservations: | + | * //Submissions// versus |
- | * Submission: | + | * //Submission//: To get the resources as soon as possible. You do not control when the job will be scheduled, and as long as the job hasn't started, the schedule may change. You may get the resources right now if OAR can (and decides to) schedule the job immediately, |
- | * Reservation; | + | * //Reservation//; you ask for resources at a specific date. __With a // |
- | * interactive | + | * // |
- | * in the non interactive case, you provide an executable which will be executed by oar on airlock during your job. This executable can be anything, a "sleep infinity" | + | * in the //non interactive// case, you provide an executable which will be executed by OAR on airlock during your job. This executable can be anything, a '' |
- | * in the interactive case, the executable is actually an interactive subshell started by oar on airlock. Beware, if this subshell terminates, the job will be killed as well (you can prevent that by running interactive submissions inside a [[https:// | + | * in the //interactive// case, the executable is actually an interactive subshell started by OAR on airlock. Beware, if this subshell terminates, the job will be killed as well (you can prevent that by running interactive submissions inside a [[https:// |
+ | Note that almost all OAR jobs terminate with status "// | ||
==== A note on energy saving ==== | ==== A note on energy saving ==== | ||
- | When nodes are unused, and after a timeout, they will be automatically shutdown (and will appear as "standby" in the drawgantt) | + | When nodes are unused, and after a timeout, they will be automatically shutdown (and will appear as "//Standby//" in the drawgantt) |
- | When a job is submitted, shutdown nodes are waken up. Thus the job will not start immediately, | + | When a job is submitted, shutdown nodes are waken up. Thus the job will not start immediately, |
- | When there is a reservation, | + | When a job is a reservation, |
+ | Since energy saving is active, it is strongly encouraged to submit/ | ||
==== Advanced usage: sharing the platform ==== | ==== Advanced usage: sharing the platform ==== | ||
reserve.1662653995.txt.gz · Last modified: 2022/09/08 18:19 by mimbert