Revision 7ed400f0 man/gnt-instance.rst

b/man/gnt-instance.rst
27 27
^^^
28 28

  
29 29
| **add**
30
| {-t|--disk-template {diskless | file \| plain \| drbd}}
30
| {-t|--disk-template {diskless | file \| plain \| drbd \| rbd}}
31 31
| {--disk=*N*: {size=*VAL* \| adopt=*LV*}[,vg=*VG*][,metavg=*VG*][,mode=*ro\|rw*]
32 32
|  \| {-s|--os-size} *SIZE*}
33 33
| [--no-ip-check] [--no-name-check] [--no-start] [--no-install]
......
588 588
drbd
589 589
    Disk devices will be drbd (version 8.x) on top of lvm volumes.
590 590

  
591
rbd
592
    Disk devices will be rbd volumes residing inside a RADOS cluster.
593

  
591 594

  
592 595
The optional second value of the ``-n (--node)`` is used for the drbd
593 596
template type and specifies the remote node.
......
1321 1324
{*amount*}
1322 1325

  
1323 1326
Grows an instance's disk. This is only possible for instances having a
1324
plain or drbd disk template.
1327
plain, drbd or rbd disk template.
1325 1328

  
1326 1329
Note that this command only change the block device size; it will not
1327 1330
grow the actual filesystems, partitions, etc. that live on that
......
1341 1344
to the arguments in the create instance operation, with a suffix
1342 1345
denoting the unit.
1343 1346

  
1344
Note that the disk grow operation might complete on one node but fail
1345
on the other; this will leave the instance with different-sized LVs on
1346
the two nodes, but this will not create problems (except for unused
1347
space).
1347
For instances with a drbd template, note that the disk grow operation
1348
might complete on one node but fail on the other; this will leave the
1349
instance with different-sized LVs on the two nodes, but this will not
1350
create problems (except for unused space).
1348 1351

  
1349 1352
If you do not want gnt-instance to wait for the new disk region to be
1350 1353
synced, use the ``--no-wait-for-sync`` option.
......
1401 1404
FAILOVER
1402 1405
^^^^^^^^
1403 1406

  
1404
**failover** [-f] [--ignore-consistency] [--shutdown-timeout=*N*]
1405
[--submit] [--ignore-ipolicy] {*instance*}
1407
| **failover** [-f] [--ignore-consistency] [--ignore-ipolicy]
1408
| [--shutdown-timeout=*N*]
1409
| [{-n|--target-node} *node* \| {-I|--iallocator} *name*]
1410
| [--submit]
1411
| {*instance*}
1406 1412

  
1407 1413
Failover will stop the instance (if running), change its primary node,
1408 1414
and if it was originally running it will start it again (on the new
1409 1415
primary). This only works for instances with drbd template (in which
1410 1416
case you can only fail to the secondary node) and for externally
1411
mirrored templates (shared storage) (which can change to any other
1417
mirrored templates (blockdev and rbd) (which can change to any other
1412 1418
node).
1413 1419

  
1420
If the instance's disk template is of type blockdev or rbd, then you
1421
can explicitly specify the target node (which can be any node) using
1422
the ``-n`` or ``--target-node`` option, or specify an iallocator plugin
1423
using the ``-I`` or ``--iallocator`` option. If you omit both, the default
1424
iallocator will be used to specify the target node.
1425

  
1414 1426
Normally the failover will check the consistency of the disks before
1415 1427
failing over the instance. If you are trying to migrate instances off
1416 1428
a dead node, this will fail. Use the ``--ignore-consistency`` option
......
1443 1455

  
1444 1456
**migrate** [-f] [--allow-failover] [--non-live]
1445 1457
[--migration-mode=live\|non-live] [--ignore-ipolicy]
1446
[--no-runtime-changes] {*instance*}
1447

  
1448
Migrate will move the instance to its secondary node without
1449
shutdown. It only works for instances having the drbd8 disk template
1450
type.
1458
[--no-runtime-changes]
1459
[{-n|--target-node} *node* \| {-I|--iallocator} *name*] {*instance*}
1460

  
1461
Migrate will move the instance to its secondary node without shutdown.
1462
As with failover, it only works for instances having the drbd disk
1463
template or an externally mirrored disk template type such as blockdev
1464
or rbd.
1465

  
1466
If the instance's disk template is of type blockdev or rbd, then you can
1467
explicitly specify the target node (which can be any node) using the
1468
``-n`` or ``--target-node`` option, or specify an iallocator plugin
1469
using the ``-I`` or ``--iallocator`` option. If you omit both, the
1470
default iallocator will be used to specify the target node.
1451 1471

  
1452 1472
The migration command needs a perfectly healthy instance, as we rely
1453 1473
on the dual-master capability of drbd8 and the disks of the instance

Also available in: Unified diff