Revision b24e516d
| b/man/hroller.rst | ||
|---|---|---|
| 94 | 94 |
are migrated from node to node) are not supported yet. Hroller by design |
| 95 | 95 |
should support them both with and without secondary node replacement. |
| 96 | 96 |
|
| 97 |
EXAMPLE |
|
| 98 |
------- |
|
| 97 |
EXAMPLES |
|
| 98 |
-------- |
|
| 99 |
|
|
| 100 |
Online Rolling reboots, using tags |
|
| 101 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
| 102 |
|
|
| 103 |
Selecting by tags and getting output for one step only can be used for |
|
| 104 |
planing the next maintenance step. |
|
| 105 |
:: |
|
| 106 |
|
|
| 107 |
$ hroller --node-tags needsreboot --one-step-only -L |
|
| 108 |
'First Reboot Group' |
|
| 109 |
node1.example.com |
|
| 110 |
node3.example.com |
|
| 111 |
|
|
| 112 |
Typically these nodes would be drained and migrated. |
|
| 113 |
:: |
|
| 114 |
|
|
| 115 |
$ GROUP=`hroller --node-tags needsreboot --one-step-only --no-headers -L` |
|
| 116 |
$ for node in $GROUP; do gnt-node modify -D yes $node; done |
|
| 117 |
$ for node in $GROUP; do gnt-node migrate -f --submit $node; done |
|
| 118 |
|
|
| 119 |
After maintenance, the tags would be removed and the nodes undrained. |
|
| 120 |
|
|
| 99 | 121 |
|
| 100 |
Rolling node reboot output |
|
| 101 |
~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
| 122 |
Offline Rolling node reboot output
|
|
| 123 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
| 102 | 124 |
|
| 103 |
With the default options, the program shows one reboot group per line as |
|
| 104 |
a comma-separated list. |
|
| 125 |
If all instances are shut down, usually larger node groups can be found. |
|
| 105 | 126 |
:: |
| 106 | 127 |
|
| 107 |
$ hroller -L |
|
| 128 |
$ hroller --offline-maintainance -L
|
|
| 108 | 129 |
'Node Reboot Groups' |
| 109 | 130 |
node1.example.com,node3.example.com,node5.example.com |
| 110 | 131 |
node8.example.com,node6.example.com,node2.example.com |
Also available in: Unified diff