Revision e721c742
| b/doc/install.rst | ||
|---|---|---|
| 317 | 317 |
KVM. |
| 318 | 318 |
|
| 319 | 319 |
Beware that the default name Ganeti uses is ``xen-br0`` (which was used |
| 320 |
in Xen 2.0) while Xen 3.0 uses ``xenbr0`` by default. The default bridge
|
|
| 321 |
your Ganeti cluster will use for new instances can be specified at
|
|
| 322 |
cluster initialization time.
|
|
| 320 |
in Xen 2.0) while Xen 3.0 uses ``xenbr0`` by default. See the
|
|
| 321 |
`Initializing the cluster`_ section to learn how to choose a different
|
|
| 322 |
bridge, or not to use one at all and use "routed mode".
|
|
| 323 | 323 |
|
| 324 |
If you want to run in "routing mode" you need to specify that at cluster |
|
| 325 |
init time (using the --nicparam option), and then no bridge will be |
|
| 326 |
needed. In this mode instance traffic will be routed by dom0, instead of |
|
| 327 |
bridged. |
|
| 328 |
|
|
| 329 |
In order to use "routing mode" under Xen, you'll need to change the |
|
| 324 |
In order to use "routed mode" under Xen, you'll need to change the |
|
| 330 | 325 |
relevant parameters in the Xen config file. Under KVM instead, no config |
| 331 | 326 |
change is necessary, but you still need to set up your network |
| 332 | 327 |
interfaces correctly. |
| ... | ... | |
| 524 | 519 |
(master) node. |
| 525 | 520 |
|
| 526 | 521 |
If you want to use a bridge which is not ``xen-br0``, or no bridge at |
| 527 |
all, use ``--nicparams``. |
|
| 522 |
all, change it with the ``--nic-parameters`` option. For example to |
|
| 523 |
bridge on br0 you can say:: |
|
| 524 |
|
|
| 525 |
--nic-parameters link=br0 |
|
| 526 |
|
|
| 527 |
Or to not bridge at all, and use a separate routing table:: |
|
| 528 |
|
|
| 529 |
--nic-parameters mode=routed,link=100 |
|
| 528 | 530 |
|
| 529 |
If the bridge name you are using is not ``xen-br0``, use the *-b |
|
| 530 |
<BRIDGENAME>* option to specify the bridge name. In this case, you |
|
| 531 |
should also use the *--master-netdev <BRIDGENAME>* option with the same |
|
| 532 |
BRIDGENAME argument. |
|
| 531 |
If you don't have a xen-br0 interface you also have to specify a |
|
| 532 |
different network interface which will get the cluster ip, on the master |
|
| 533 |
node, by using the ``--master-netdev <device>`` option. |
|
| 533 | 534 |
|
| 534 | 535 |
You can use a different name than ``xenvg`` for the volume group (but |
| 535 | 536 |
note that the name must be identical on all nodes). In this case you |
Also available in: Unified diff