This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
wiki:disk_reservation [2016/11/29 23:08] – [Limits] neyron | wiki:disk_reservation [2016/11/30 10:26] – neyron | ||
---|---|---|---|
Line 2: | Line 2: | ||
E.g. Each node has " | E.g. Each node has " | ||
This would give users the capability of keeping data on disk for a longer time than the compute time, e.g. a more persistent storage for data. | This would give users the capability of keeping data on disk for a longer time than the compute time, e.g. a more persistent storage for data. | ||
+ | |||
===== Setup ===== | ===== Setup ===== | ||
We create //disk// resources, then setup some coupling so that a //compute// resource is **tagged** when a user has disks reserved on it. Tagging in done in the //disk// property of the //compute// resource (type // | We create //disk// resources, then setup some coupling so that a //compute// resource is **tagged** when a user has disks reserved on it. Tagging in done in the //disk// property of the //compute// resource (type // | ||
Line 277: | Line 278: | ||
* 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. | * 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 '' | * The '' | ||
+ | * A // | ||
+ | * While batch jobs which are not started yet will be move with regard to previous scheduling decisions, some may have started before the disk property of the resources is changed, making resources whose disks are reserved unavailable for the duration of those jobs. | ||
+ | * Advance reservations could also be accepted on the resources: resources are //booked// upon submission acceptation for an advance reservation, |