Commit 29b27463 authored by Klaus Aehlig's avatar Klaus Aehlig
Browse files

Document --max-running-jobs option of gnt-cluster modify

This option control the number of jobs in non-finalized non-queued
state and was added some time ago. Document it in the man page as
Signed-off-by: default avatarKlaus Aehlig <>
Reviewed-by: default avatarPetr Pudlak <>
parent ebd41f03
......@@ -650,6 +650,7 @@ MODIFY
| [\--add-uids *user-id pool definition*]
| [\--remove-uids *user-id pool definition*]
| [{-C|\--candidate-pool-size} *candidate\_pool\_size*]
| [--max-running-jobs *count* ]
| [\--maintain-node-health {yes \| no}]
| [\--prealloc-wipe-disks {yes \| no}]
| [{-I|\--default-iallocator} *default instance allocator*]
......@@ -688,6 +689,10 @@ described in the **init** command.
The ``--hypervisor-state`` and ``--disk-state`` options are described in
detail in **ganeti**\(7).
The ``--max-running-jobs`` options allows to set limit on the
number of jobs in non-finished jobs that are not queued, i.e.,
the number of jobs that are in waiting or running state.
The ``--add-uids`` and ``--remove-uids`` options can be used to
modify the user-id pool by adding/removing a list of user-ids or
user-id ranges.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment