This shows you the differences between two versions of the page.
| Next revisionBoth sides next revision | |||
| wiki:multi-cluster_with_priority [2016/02/20 13:23] – created neyron | wiki:multi-cluster_with_priority [2016/02/20 13:33] – neyron | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| For that purpose, you can use the scheduler_priority property of the nodes (setting it using the oarnodesetting command), which will be taken into account as specified per the | For that purpose, you can use the scheduler_priority property of the nodes (setting it using the oarnodesetting command), which will be taken into account as specified per the | ||
| SCHEDULER_RESOURCE_ORDER configuration setting in oar.conf. | SCHEDULER_RESOURCE_ORDER configuration setting in oar.conf. | ||
| + | |||
| + | |||
| + | Please mind also adding a ' | ||
| + | then oarnodesetting command) to identify cluster easly in oarsub | ||
| + | commands, if one of the concern is to not have job mix nodes from old | ||
| + | and new clusters. | ||
| + | |||
| + | e.g.: | ||
| + | $ oarsub -p " | ||
| + | |||
| + | which would be equivalent but maybe less cryptic than | ||
| + | |||
| + | $ oarsub -p " | ||
| + | |||
| + | The scheduler priority being a integer, it however allows for a -p | ||
| + | switch such as " | ||
| + | say if you have more than 3 clusters. | ||