Revision b1eb71c7 doc/design-autorepair.rst
b/doc/design-autorepair.rst | ||
---|---|---|
81 | 81 |
never vice versa (if a worse solution is allowed then so is a better |
82 | 82 |
one). |
83 | 83 |
|
84 |
If there are multiple ``ganeti:watcher:autorepair:<type>`` tags in an |
|
85 |
object (cluster, node group or instance), the least destructive tag |
|
86 |
takes precedence. When multiplicity happens across objects, the nearest |
|
87 |
tag wins. For example, if in a cluster with two instances, *I1* and |
|
88 |
*I2*, *I1* has ``failover``, and the cluster itself has both |
|
89 |
``fix-storage`` and ``reinstall``, *I1* will end up with ``failover`` |
|
90 |
and *I2* with ``fix-storage``. |
|
91 |
|
|
84 | 92 |
ganeti:watcher:autorepair:suspend[:<timestamp>] |
85 | 93 |
+++++++++++++++++++++++++++++++++++++++++++++++ |
86 | 94 |
|
... | ... | |
102 | 110 |
instances matching a filter on some charateristic. But again, this |
103 | 111 |
wouldn't be specific to this tag. |
104 | 112 |
|
113 |
If there are multiple |
|
114 |
``ganeti:watcher:autorepair:suspend[:<timestamp>]`` tags in an object, |
|
115 |
the form without timestamp takes precedence (permanent suspension); or, |
|
116 |
if all object tags have a timestamp, the one with the highest timestamp. |
|
117 |
When multiplicity happens across objects, the nearest tag wins, as |
|
118 |
above. This makes it possible to suspend cluster-enabled repairs with a |
|
119 |
single tag in the cluster object; or to suspend them only for a certain |
|
120 |
node group or instance. At the same time, it is possible to re-enable |
|
121 |
cluster-suspended repairs in a particular instance or group by applying |
|
122 |
an enable tag to them. |
|
123 |
|
|
105 | 124 |
ganeti:watcher:autorepair:pending:<type>:<id>:<timestamp>:<jobs> |
106 | 125 |
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
107 | 126 |
|
Also available in: Unified diff