reserve
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
reserve [2017/08/31 16:09] – 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 55: | Line 73: | ||
< | < | ||
+ | Despite this syntax being not user-friendly, | ||
+ | * Nodes are often shutdown, in energy saving mode. Booking only the needed nodes ensures that only these ones will be wakeup. This contributes to increase node lifetime and saving energy | ||
+ | * As only needed nodes are asked, it avoids your oar job being canceled or postponed in case one node that you don't use is unavailable | ||
+ | * It allows tracing more accurately resources usage | ||
+ | |||
+ | ==== Booking the room without any node ==== | ||
+ | |||
+ | You can book the room only, without any node with the following syntax: | ||
+ | |||
+ | < | ||
+ | |||
+ | This is useful in particular if you want to go physically in the room for experimenting with specific hardware, because it avoids waking any node if they are in energy saving mode. | ||
+ | |||
+ | ==== A note on OAR job scheduling ==== | ||
+ | |||
+ | 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 another job is running | ||
+ | * because the resources you ask are currently not available but OAR expects them to be available in the future | ||
+ | * etc. | ||
+ | So, the only reliable way to be sure that your job is actually running is to check that the job's state is "// | ||
+ | |||
+ | < | ||
+ | |||
+ | Tasks submitted to minus will never start unless the job is "// | ||
+ | |||
+ | To sum-up things: | ||
+ | * // | ||
+ | * // | ||
+ | * // | ||
+ | * // | ||
+ | * in the //non interactive// | ||
+ | * in the // | ||
+ | |||
+ | Note that almost all OAR jobs terminate with status "// | ||
+ | ==== A note on energy saving ==== | ||
+ | |||
+ | When nodes are unused, and after a timeout, they will be automatically shutdown (and will appear as "// | ||
+ | |||
+ | When a job is submitted, shutdown nodes are waken up. Thus the job will not start immediately, | ||
+ | |||
+ | 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.1504188583.txt.gz · Last modified: 2017/08/31 16:09 by mimbert