Revision 0bfbb3e8
b/hbal.1 | ||
---|---|---|
15 | 15 |
Backend options: |
16 | 16 |
.BI "[ -m " cluster " ]" |
17 | 17 |
| |
18 |
.BI "[ -L[" path "]]" |
|
18 |
.BI "[ -L[" path "] [-X]]"
|
|
19 | 19 |
| |
20 | 20 |
.BI "[ -n " nodes-file " ]" |
21 | 21 |
.BI "[ -i " instances-file " ]" |
... | ... | |
175 | 175 |
.B -C, --print-commands |
176 | 176 |
Print the command list at the end of the run. Without this, the |
177 | 177 |
program will only show a shorter, but cryptic output. |
178 |
|
|
179 |
Note that the moves list will be split into independent steps, called |
|
180 |
"jobsets", but only for visual inspection, not for actually |
|
181 |
parallelisation. It is not possible to parallelise these directly when |
|
182 |
executed via "gnt-instance" commands, since a compound command |
|
183 |
(e.g. failover and replace-disks) must be executed serially. Parallel |
|
184 |
execution is only possible when using the Luxi backend and the |
|
185 |
\fI-L\fR option. |
|
186 |
|
|
187 |
The algorithm for splitting the moves into jobsets is by accumulating |
|
188 |
moves until the next move is touching nodes already touched by the |
|
189 |
current moves; this means we can't execute in parallel (due to |
|
190 |
resource allocation in Ganeti) and thus we start a new jobset. |
|
191 |
|
|
178 | 192 |
.TP |
179 | 193 |
.B -p, --print-nodes |
180 | 194 |
Prints the before and after node status, in a format designed to allow |
... | ... | |
340 | 354 |
used by ganeti when installed with "--localstatedir=/var" is used. |
341 | 355 |
|
342 | 356 |
.TP |
357 |
.B "-X" |
|
358 |
When using the Luxi backend, hbal can also execute the given |
|
359 |
commands. The execution method is to execute the individual jobsets |
|
360 |
(see the \fI-C\fR option for details) in separate stages, aborting if |
|
361 |
at any time a jobset doesn't have all jobs successful. Each step in |
|
362 |
the balancing solution will be translated into exactly one Ganeti job |
|
363 |
(having between one and three OpCodes), and all the steps in a jobset |
|
364 |
will be executed in parallel. The jobsets themselves are executed |
|
365 |
serially. |
|
366 |
|
|
367 |
.TP |
|
343 | 368 |
.BI "-l" N ", --max-length=" N |
344 | 369 |
Restrict the solution to this length. This can be used for example to |
345 | 370 |
automate the execution of the balancing. |
Also available in: Unified diff