reserve
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
reserve [2016/12/12 11:08] – onicolas | reserve [2017/08/30 16:31] – [Advanced usage: sharing the platform] mimbert | ||
---|---|---|---|
Line 8: | Line 8: | ||
The role of //OAR// is to schedule node reservations. It manages **jobs** associated with users. A job has a start time, a duration (walltime), and uses some resources (CorteXlab nodes). | The role of //OAR// is to schedule node reservations. It manages **jobs** associated with users. A job has a start time, a duration (walltime), and uses some resources (CorteXlab nodes). | ||
+ | |||
+ | ==== Submissions ==== | ||
The principle of operation of CorteXlab is that users submit jobs to OAR. When the job starts, the user gets exclusive access to the platform, and inside an OAR job, the user can perform (interactively, | The principle of operation of CorteXlab is that users submit jobs to OAR. When the job starts, the user gets exclusive access to the platform, and inside an OAR job, the user can perform (interactively, | ||
Line 21: | Line 23: | ||
This command will wait for the resources to be available, and as soon as they are (i.e. -I stands for interactive), | This command will wait for the resources to be available, and as soon as they are (i.e. -I stands for interactive), | ||
- | By default OAR submissions are scheduled as soon as possible. It is also possible | + | Submissions may not be interactive. You can provide a script name to execute when the job starts. It has the strong advantage that it allows you to avoid waiting |
+ | < | ||
+ | |||
+ | A particular case of this syntax is: | ||
+ | |||
+ | < | ||
+ | |||
+ | It allows you to have a job which is not tied to a terminal, but you still need to manually submit minus tasks when the job starts | ||
+ | |||
+ | ==== Reservations ==== | ||
+ | |||
+ | By default OAR submissions are scheduled as soon as possible. It is also possible to ask for an OAR // | ||
This other simple example is reserving all the nodes on the 18 of September 2015 from 10AM to 11AM: | This other simple example is reserving all the nodes on the 18 of September 2015 from 10AM to 11AM: | ||
Line 28: | Line 41: | ||
< | < | ||
- | This command will wait for the resources to be available, and as soon as they are, a job is allocated, is started, and a subshell is instantiated where you can work on experiments. As soon as the subshell is closed, the job ends. (It can be useful to work in a [screen](https:// | + | ==== Booking specific nodes ==== |
- | By default OAR submissions | + | If you want to reserve specific nodes, there are several |
+ | |||
+ | To make a submission using two nodes: | ||
+ | |||
+ | < | ||
+ | |||
+ | But the nodes will be randomly chosen by OAR, so you'll have to adapt your task's scenario to the allocated nodes. | ||
+ | |||
+ | It is possible to ask for explicit nodes with a less user-friendly syntax (especially in situations where you need lots of nodes). For example, to make a submission using specifically nodes 4 and 6, for a 30 minutes job: | ||
+ | |||
+ | < | ||
+ | |||
+ | ==== Advanced usage: sharing the platform ==== | ||
+ | |||
+ | It is possible to share the platform, for specific situations such as tutorials, courses, challenges. In these situations, | ||
+ | |||
+ | The organizer of the tutorial/ | ||
+ | |||
+ | < | ||
+ | |||
+ | This will reserve all available nodes for a 4 hours event, between 14 and 18 on July 21, 2018. | ||
+ | |||
+ | Then, participants can submit jobs inside the container job with this (example) syntax: | ||
+ | |||
+ | < | ||
+ | |||
+ | or (another example): | ||
+ | |||
+ | < | ||
+ | |||
+ | alternatively, | ||
+ | |||
+ | < | ||
+ | |||
+ | Then, participants will have to use: | ||
+ | |||
+ | < | ||
+ | |||
+ | ==== OAR Documentation ==== | ||
+ | The complete OAR documentation, |
reserve.txt · Last modified: 2022/11/18 16:43 by pgirard