root / man / hroller.rst @ a39779f6
History | View | Annotate | Download (2.6 kB)
| 1 |
HROLLER(1) Ganeti | Version @GANETI_VERSION@ |
|---|---|
| 2 |
============================================ |
| 3 |
|
| 4 |
NAME |
| 5 |
---- |
| 6 |
|
| 7 |
hroller \- Cluster rolling maintenance scheduler for Ganeti |
| 8 |
|
| 9 |
SYNOPSIS |
| 10 |
-------- |
| 11 |
|
| 12 |
**hroller** {backend options...} [algorithm options...] [reporting options...]
|
| 13 |
|
| 14 |
**hroller** \--version |
| 15 |
|
| 16 |
|
| 17 |
Backend options: |
| 18 |
|
| 19 |
{ **-m** *cluster* | **-L[** *path* **]** | **-t** *data-file* |
|
| 20 |
**-I** *path* } |
| 21 |
|
| 22 |
**[ --force ]** |
| 23 |
|
| 24 |
Algorithm options: |
| 25 |
|
| 26 |
**[ -G *name* ]** |
| 27 |
|
| 28 |
**[ -O *name...* ]** |
| 29 |
|
| 30 |
**[ --node-tags** *tag,..* **]** |
| 31 |
|
| 32 |
Reporting options: |
| 33 |
|
| 34 |
**[ -v... | -q ]** |
| 35 |
**[ -S *file* ]** |
| 36 |
|
| 37 |
DESCRIPTION |
| 38 |
----------- |
| 39 |
|
| 40 |
hroller is a cluster maintenance reboot scheduler. It can calculate |
| 41 |
which set of nodes can be rebooted at the same time while avoiding |
| 42 |
having both primary and secondary nodes being rebooted at the same time. |
| 43 |
|
| 44 |
For backends that support identifying the master node (currenlty |
| 45 |
RAPI and LUXI), the master node is scheduled as the last node |
| 46 |
in the last reboot group. Apart from this restriction, larger reboot |
| 47 |
groups are put first. |
| 48 |
|
| 49 |
ALGORITHM FOR CALCULATING OFFLINE REBOOT GROUPS |
| 50 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 51 |
|
| 52 |
hroller will view the nodes as vertices of an undirected graph, |
| 53 |
connecting by instances which have both a primary and a secondary node. |
| 54 |
It will then color the graph using a few different heuristics, and |
| 55 |
return the minimum-size color set found. Node with the same color don't |
| 56 |
share an edge, and as such don't have an instance with both primary and |
| 57 |
secondary node on them, so they are safe to be rebooted concurrently. |
| 58 |
|
| 59 |
OPTIONS |
| 60 |
------- |
| 61 |
|
| 62 |
For a description of the standard options check **htools**\(7) and |
| 63 |
**hbal**\(1). |
| 64 |
|
| 65 |
\--node-tags *tag,...* |
| 66 |
Restrict to nodes having at least one of the given tags. |
| 67 |
|
| 68 |
\--force |
| 69 |
Do not fail, even if the master node cannot be determined. |
| 70 |
|
| 71 |
|
| 72 |
BUGS |
| 73 |
---- |
| 74 |
|
| 75 |
Offline nodes should be ignored. |
| 76 |
|
| 77 |
If instances are online the tool should refuse to do offline rolling |
| 78 |
maintenances, unless explicitly requested. |
| 79 |
|
| 80 |
End-to-end shelltests should be provided. |
| 81 |
|
| 82 |
Online rolling maintenances (where instance need not be shut down, but |
| 83 |
are migrated from node to node) are not supported yet. Hroller by design |
| 84 |
should support them both with and without secondary node replacement. |
| 85 |
|
| 86 |
EXAMPLE |
| 87 |
------- |
| 88 |
|
| 89 |
Offline Rolling node reboot output |
| 90 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 91 |
|
| 92 |
With the default options, the program shows one reboot group per line as |
| 93 |
a comma-separated list. |
| 94 |
:: |
| 95 |
|
| 96 |
$ hroller -L |
| 97 |
'Node Reboot Groups' |
| 98 |
node1.example.com,node3.example.com,node5.example.com |
| 99 |
node8.example.com,node6.example.com,node2.example.com |
| 100 |
node7.example.com,node4.example.com |
| 101 |
|
| 102 |
.. vim: set textwidth=72 : |
| 103 |
.. Local Variables: |
| 104 |
.. mode: rst |
| 105 |
.. fill-column: 72 |
| 106 |
.. End: |