Revision 240c769f
b/doc/install.rst | ||
---|---|---|
552 | 552 |
|
553 | 553 |
You can use a different name than ``xenvg`` for the volume group (but |
554 | 554 |
note that the name must be identical on all nodes). In this case you |
555 |
need to specify it by passing the *-g <VGNAME>* option to ``gnt-cluster
|
|
556 |
init``. |
|
555 |
need to specify it by passing the *--vg-name <VGNAME>* option to
|
|
556 |
``gnt-cluster init``.
|
|
557 | 557 |
|
558 | 558 |
To set up the cluster as an Xen HVM cluster, use the |
559 | 559 |
``--enabled-hypervisors=xen-hvm`` option to enable the HVM hypervisor |
b/doc/walkthrough.rst | ||
---|---|---|
789 | 789 |
|
790 | 790 |
As you can see, *instance4* has a copy running on node3, because we |
791 | 791 |
forced the failover when node3 failed. This case is dangerous as the |
792 |
instance will have the same IP and MAC address, wreaking havok on the
|
|
792 |
instance will have the same IP and MAC address, wreaking havoc on the
|
|
793 | 793 |
network environment and anyone who tries to use it. |
794 | 794 |
|
795 | 795 |
Ganeti doesn't directly handle this case. It is recommended to logon to |
Also available in: Unified diff