Revision 172679c9
| b/doc/iallocator.rst | ||
|---|---|---|
| 190 | 190 |
|
| 191 | 191 |
type |
| 192 | 192 |
the request type; this can be either ``allocate``, ``relocate``, |
| 193 |
``multi-relocate`` or ``multi-evacuate``. The ``allocate`` request
|
|
| 194 |
is used when a new instance needs to be placed on the cluster. The
|
|
| 195 |
``relocate`` request is used when an existing instance needs to be
|
|
| 196 |
moved within its node group. |
|
| 193 |
``change-group``, ``node-evacuate`` or ``multi-evacuate``. The
|
|
| 194 |
``allocate`` request is used when a new instance needs to be placed
|
|
| 195 |
on the cluster. The ``relocate`` request is used when an existing
|
|
| 196 |
instance needs to be moved within its node group.
|
|
| 197 | 197 |
|
| 198 | 198 |
The ``multi-evacuate`` protocol used to request that the script |
| 199 | 199 |
computes the optimal relocate solution for all secondary instances |
| ... | ... | |
| 330 | 330 |
entry in the input message, otherwise Ganeti will consider the result |
| 331 | 331 |
as failed |
| 332 | 332 |
|
| 333 |
for multi-relocate mode, this is a list of lists of serialized |
|
| 334 |
opcodes; see the :ref:`design document <multi-reloc-result>` for a |
|
| 335 |
detailed description |
|
| 333 |
for the ``node-evacuate`` and ``change-group`` modes, this is a |
|
| 334 |
dictionary containing, among other information, a list of lists of |
|
| 335 |
serialized opcodes; see the :ref:`design document |
|
| 336 |
<multi-reloc-result>` for a detailed description |
|
| 336 | 337 |
|
| 337 | 338 |
for multi-evacuation mode, this is a list of lists; each element of |
| 338 | 339 |
the list is a list of instance name and the new secondary node |
Also available in: Unified diff