Revision 7ed400f0 doc/admin.rst
| b/doc/admin.rst | ||
|---|---|---|
| 115 | 115 |
the instance sees the same virtual drive in all cases, the node-level |
| 116 | 116 |
configuration varies between them. |
| 117 | 117 |
|
| 118 |
There are four disk templates you can choose from:
|
|
| 118 |
There are five disk templates you can choose from:
|
|
| 119 | 119 |
|
| 120 | 120 |
diskless |
| 121 | 121 |
The instance has no disks. Only used for special purpose operating |
| ... | ... | |
| 138 | 138 |
to obtain a highly available instance that can be failed over to a |
| 139 | 139 |
remote node should the primary one fail. |
| 140 | 140 |
|
| 141 |
rbd |
|
| 142 |
The instance will use Volumes inside a RADOS cluster as backend for its |
|
| 143 |
disks. It will access them using the RADOS block device (RBD). |
|
| 144 |
|
|
| 141 | 145 |
IAllocator |
| 142 | 146 |
~~~~~~~~~~ |
| 143 | 147 |
|
| ... | ... | |
| 510 | 514 |
target node, or the operation will fail if that's not possible. See |
| 511 | 515 |
:ref:`instance-startup-label` for details. |
| 512 | 516 |
|
| 517 |
If the instance's disk template is of type rbd, then you can specify |
|
| 518 |
the target node (which can be any node) explicitly, or specify an |
|
| 519 |
iallocator plugin. If you omit both, the default iallocator will be |
|
| 520 |
used to determine the target node:: |
|
| 521 |
|
|
| 522 |
gnt-instance failover -n TARGET_NODE INSTANCE_NAME |
|
| 523 |
|
|
| 513 | 524 |
Live migrating an instance |
| 514 | 525 |
~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 515 | 526 |
|
| ... | ... | |
| 530 | 541 |
which case the target node should have at least the instance's current |
| 531 | 542 |
runtime memory free. |
| 532 | 543 |
|
| 544 |
If the instance's disk template is of type rbd, then you can specify |
|
| 545 |
the target node (which can be any node) explicitly, or specify an |
|
| 546 |
iallocator plugin. If you omit both, the default iallocator will be |
|
| 547 |
used to determine the target node:: |
|
| 548 |
|
|
| 549 |
gnt-instance migrate -n TARGET_NODE INSTANCE_NAME |
|
| 550 |
|
|
| 533 | 551 |
Moving an instance (offline) |
| 534 | 552 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 535 | 553 |
|
| ... | ... | |
| 1247 | 1265 |
6. Remove the ganeti state directory (``rm -rf /var/lib/ganeti/*``), |
| 1248 | 1266 |
replacing the path with the correct path for your installation. |
| 1249 | 1267 |
|
| 1268 |
7. If using RBD, run ``rbd unmap /dev/rbdN`` to unmap the RBD disks. |
|
| 1269 |
Then remove the RBD disk images used by Ganeti, identified by their |
|
| 1270 |
UUIDs (``rbd rm uuid.rbd.diskN``). |
|
| 1271 |
|
|
| 1250 | 1272 |
On the master node, remove the cluster from the master-netdev (usually |
| 1251 | 1273 |
``xen-br0`` for bridged mode, otherwise ``eth0`` or similar), by running |
| 1252 | 1274 |
``ip a del $clusterip/32 dev xen-br0`` (use the correct cluster ip and |
Also available in: Unified diff