Differences

This shows you the differences between two versions of the page.

--- wiki:disk_reservation [2016/11/29 23:01] – [Server prologue/epilogue] neyron
+++ wiki:disk_reservation [2016/11/29 23:08] – [Limits] neyron
@@ Line 156: / Line 156: @@
 Mind setting a relevant priority for the new admission rule.
-Finally, just like for deploy jobs, we allow only whole nodes for //compute with disk// jobs. For that, we edit the corresponding rule: ''oaradmissionrules -m 9 -e''
+Finally, just like for deploy jobs, we might want to allow only whole nodes for //compute with disk// jobs. For that, we edit the corresponding rule: ''oaradmissionrules -m 9 -e''
 <code perl>
 -# Restrict allowed properties for deploy jobs to force requesting entire nodes
@@ Line 276: / Line 276: @@
   * This workaround does not allow to place and show (schedule) the //compute// jobs in the future (i.e. before the //disk// job is running)... While not scheduled, //compute// jobs can be submitted ahead of time however. Also the scheduling decision could place //compute// jobs after the end of the running //disk// job, so that they would actually not launch in fine.
   * Users may want to select specific disks/hosts when using only a part of the reserved disks for a given compute job. This mechanism does not allow it.
+  * The ''reserve_disk'' and ''with_disk'' job types do not allow to reserve at once (in a single ''oarsub'' command) both the disk and compute resources.