Commit f4664f19 authored by Klaus Aehlig's avatar Klaus Aehlig

Document the --sequential option

Document that group evacuation is usually run in parallel, but
can be made sequentially by providing an appropriate option.
Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
parent c812ab71
...@@ -187,7 +187,7 @@ options. ...@@ -187,7 +187,7 @@ options.
EVACUATE EVACUATE
~~~~~~~~ ~~~~~~~~
| **evacuate** [\--submit] [\--print-job-id] | **evacuate** [\--submit] [\--print-job-id] [\--sequential]
| [\--iallocator *NAME*] [\--to *GROUP*...] {*group*} | [\--iallocator *NAME*] [\--to *GROUP*...] {*group*}
This command will move all instances out of the given node group. This command will move all instances out of the given node group.
...@@ -197,6 +197,12 @@ the command line or as a cluster default. ...@@ -197,6 +197,12 @@ the command line or as a cluster default.
If no specific destination groups are specified using ``--to``, all If no specific destination groups are specified using ``--to``, all
groups except the evacuated group are considered. groups except the evacuated group are considered.
The moves of the individual instances are handled as separate jobs
to allow for maximal parallelism. If the ``--sequential`` option is
given, the moves of the individual instances will be executed sequentially.
This can be usefull if the link between the groups is vulnerable to
congestion.
See **ganeti**\(7) for a description of ``--submit`` and other common See **ganeti**\(7) for a description of ``--submit`` and other common
options. options.
......
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