Revision 9f83899a doc/install.rst

b/doc/install.rst
326 326

  
327 327
**Mandatory** on all nodes.
328 328

  
329
Ganeti relies on Xen running in "bridge mode", which means the
330
instances network interfaces will be attached to a software bridge
331
running in dom0. Xen by default creates such a bridge at startup, but
332
your distribution might have a different way to do things.
329
You can run Ganeti either in "bridge mode" or in "routed mode". In bridge
330
mode, the default, the instances network interfaces will be attached to a
331
software bridge running in dom0. Xen by default creates such a bridge at
332
startup, but your distribution might have a different way to do things, and
333
you'll definitely need to manually set it up under KVM.
333 334

  
334 335
Beware that the default name Ganeti uses is ``xen-br0`` (which was
335 336
used in Xen 2.0) while Xen 3.0 uses ``xenbr0`` by default. The default
336 337
bridge your Ganeti cluster will use for new instances can be specified
337 338
at cluster initialization time.
338 339

  
339
.. admonition:: Debian
340
If you want to run in "routing mode" you need to specify that at cluster init
341
time (using the --nicparam option), and then no bridge will be needed. In
342
this mode instance traffic will be routed by dom0, instead of bridged.
343

  
344
In order to use "routing mode" under Xen, you'll need to change the relevant
345
parameters in the Xen config file. Under KVM instead, no config change is
346
necessary, but you still need to set up your network interfaces correctly.
347

  
348
By default, under KVM, the "link" parameter you specify per-nic will
349
represent, if non-empty, a different routing table name or number to use for
350
your instances. This allows insulation between different instance groups,
351
and different routing policies between node traffic and instance traffic.
352

  
353
You will need to configure your routing table basic routes and rules outside
354
of ganeti. The vif scripts will only add /32 routes to your instances,
355
through their interface, in the table you specified (under KVM, and in the
356
main table under Xen).
357

  
358
.. admonition:: Bridging under Debian
340 359

  
341 360
   The recommended way to configure the Xen bridge is to edit your
342 361
   ``/etc/network/interfaces`` file and substitute your normal
......
493 512
**exclusively** for this purpose, and cannot be the name of the first
494 513
(master) node.
495 514

  
515
If you want to use a bridge which is not ``xen-br0``, or no bridge at all, use
516
the --nicparams
517

  
496 518
If the bridge name you are using is not ``xen-br0``, use the *-b
497 519
<BRIDGENAME>* option to specify the bridge name. In this case, you
498 520
should also use the *--master-netdev <BRIDGENAME>* option with the

Also available in: Unified diff