cluster, indexed by instance name; the contents are similar to the
instance definitions for the allocate mode, with the addition of:
- admin_up
+ admin_state
if this instance is set to run (but not the actual status of the
instance)
type
the request type; this can be either ``allocate``, ``relocate``,
- ``change-group``, ``node-evacuate`` or ``multi-evacuate``. The
+ ``change-group`` or ``node-evacuate``. The
``allocate`` request is used when a new instance needs to be placed
on the cluster. The ``relocate`` request is used when an existing
instance needs to be moved within its node group.
The ``multi-evacuate`` protocol used to request that the script
computes the optimal relocate solution for all secondary instances
- of the given nodes. It is now deprecated and should no longer be
- used.
+ of the given nodes. It is now deprecated and needs only be
+ implemented if backwards compatibility with Ganeti 2.4 and lower is
+ needed.
The ``change-group`` request is used to relocate multiple instances
across multiple node groups. ``node-evacuate`` evacuates instances
should be considered for relocating instances to; type
*list of strings*
-Finally, in the case of multi-evacuate, there's one single request
-argument (in addition to ``type``):
-
- evac_nodes
- the names of the nodes to be evacuated; type *list of strings*
-
Response message
~~~~~~~~~~~~~~~~
serialized opcodes; see the :ref:`design document
<multi-reloc-result>` for a detailed description
- for multi-evacuation mode, this is a list of lists; each element of
- the list is a list of instance name and the new secondary node
-
.. note:: Current Ganeti version accepts either ``result`` or ``nodes``
as a backwards-compatibility measure (older versions only supported
``nodes``)
}
}
-Input message, node evacuation::
-
- {
- "version": 2,
- ...
- "request": {
- "type": "multi-evacuate",
- "evac_nodes": [
- "node2"
- ],
- }
- }
-
Response messages
~~~~~~~~~~~~~~~~~