Revision 0b71067a
b/doc/design-multi-reloc.rst | ||
---|---|---|
72 | 72 |
|
73 | 73 |
The two lists of instances describe which instances could be |
74 | 74 |
moved/migrated and which couldn't for some reason ("unsuccessful"). The |
75 |
union of the two lists must be equal to the set of instances given in |
|
76 |
the original request. |
|
75 |
union of the instances in the two lists must be equal to the set of |
|
76 |
instances given in the original request. The successful list of |
|
77 |
instances contains elements as follows:: |
|
78 |
|
|
79 |
(instance name, target group name, [chosen node names]) |
|
80 |
|
|
81 |
The choice of names is simply for readability reasons (for example, |
|
82 |
Ganeti could log the computed solution in the job information) and for |
|
83 |
being able to check (manually) for consistency that the generated |
|
84 |
opcodes match the intended target groups/nodes. Note that for the |
|
85 |
node-evacuate operation, the group is not changed, but it should still |
|
86 |
be returned as such (as it's easier to have the same return type for |
|
87 |
both operations). |
|
88 |
|
|
89 |
The unsuccessful list of instances contains elements as follows:: |
|
90 |
|
|
91 |
(instance name, explanation) |
|
92 |
|
|
93 |
where ``explanation`` is a string describing why the plugin was not able |
|
94 |
to relocate the instance. |
|
77 | 95 |
|
78 | 96 |
The list of jobsets contained in the result describe how to actually |
79 | 97 |
execute the operation. Each jobset contains lists of serialized opcodes. |
Also available in: Unified diff