aurora_cluster:how_scheduling_works
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
aurora_cluster:how_scheduling_works [2019/03/18 09:10] florido [Suggestion to self-regulate the usage inside a project] |
aurora_cluster:how_scheduling_works [2019/03/18 09:16] florido [Suggestion to self-regulate the usage inside a project] |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| * The project members should interact on a regular basis to understand what are their expected computing needs; | * The project members should interact on a regular basis to understand what are their expected computing needs; | ||
| - | * Those negotiated needs should be translated into *expected resource requests* | + | * Those negotiated needs should be translated into **expected resource requests** |
| * These requests should be documented somewhere FIXME on the cluster, like in a file. | * These requests should be documented somewhere FIXME on the cluster, like in a file. | ||
| * All users should honour the expected resource requests from the above file when submitting | * All users should honour the expected resource requests from the above file when submitting | ||
| * In order to preserve the possibility to use all of the nodes when needed, these requests should be flexible enough to be changed on the fly according to needs of the members of the project | * In order to preserve the possibility to use all of the nodes when needed, these requests should be flexible enough to be changed on the fly according to needs of the members of the project | ||
aurora_cluster/how_scheduling_works.txt ยท Last modified: 2019/08/27 10:28 by florido
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
