Revision 7faf5110 doc/install.rst
b/doc/install.rst | ||
---|---|---|
108 | 108 |
|
109 | 109 |
.. admonition:: Why a fully qualified host name |
110 | 110 |
|
111 |
Although most distributions use only the short name in the /etc/hostname |
|
112 |
file, we still think Ganeti nodes should use the full name. The reason for |
|
113 |
this is that calling 'hostname --fqdn' requires the resolver library to work |
|
114 |
and is a 'guess' via heuristics at what is your domain name. Since Ganeti |
|
115 |
can be used among other things to host DNS servers, we don't want to depend |
|
116 |
on them as much as possible, and we'd rather have the uname() syscall return |
|
117 |
the full node name. |
|
118 |
|
|
119 |
We haven't ever found any breakage in using a full hostname on a Linux |
|
120 |
system, and anyway we recommend to have only a minimal installation on |
|
121 |
Ganeti nodes, and to use instances (or other dedicated machines) to run the |
|
122 |
rest of your network services. By doing this you can change the |
|
123 |
/etc/hostname file to contain an FQDN without the fear of breaking anything |
|
124 |
unrelated. |
|
111 |
Although most distributions use only the short name in the |
|
112 |
/etc/hostname file, we still think Ganeti nodes should use the full |
|
113 |
name. The reason for this is that calling 'hostname --fqdn' requires |
|
114 |
the resolver library to work and is a 'guess' via heuristics at what |
|
115 |
is your domain name. Since Ganeti can be used among other things to |
|
116 |
host DNS servers, we don't want to depend on them as much as |
|
117 |
possible, and we'd rather have the uname() syscall return the full |
|
118 |
node name. |
|
119 |
|
|
120 |
We haven't ever found any breakage in using a full hostname on a |
|
121 |
Linux system, and anyway we recommend to have only a minimal |
|
122 |
installation on Ganeti nodes, and to use instances (or other |
|
123 |
dedicated machines) to run the rest of your network services. By |
|
124 |
doing this you can change the /etc/hostname file to contain an FQDN |
|
125 |
without the fear of breaking anything unrelated. |
|
125 | 126 |
|
126 | 127 |
|
127 | 128 |
Installing The Hypervisor |
... | ... | |
130 | 131 |
**Mandatory** on all nodes. |
131 | 132 |
|
132 | 133 |
While Ganeti is developed with the ability to modularly run on different |
133 |
virtualization environments in mind the only two currently useable on a live
|
|
134 |
system are Xen and KVM. Supported Xen versions are: 3.0.3, 3.0.4 and 3.1.
|
|
135 |
Supported KVM version are 72 and above. |
|
134 |
virtualization environments in mind the only two currently useable on a |
|
135 |
live system are Xen and KVM. Supported Xen versions are: 3.0.3, 3.0.4
|
|
136 |
and 3.1. Supported KVM version are 72 and above.
|
|
136 | 137 |
|
137 | 138 |
Please follow your distribution's recommended way to install and set |
138 | 139 |
up Xen, or install Xen from the upstream source, if you wish, |
... | ... | |
140 | 141 |
kernel and the KVM tools. |
141 | 142 |
|
142 | 143 |
After installing Xen, you need to reboot into your new system. On some |
143 |
distributions this might involve configuring GRUB appropriately, whereas others
|
|
144 |
will configure it automatically when you install the respective kernels. For
|
|
145 |
KVM no reboot should be necessary. |
|
144 |
distributions this might involve configuring GRUB appropriately, whereas |
|
145 |
others will configure it automatically when you install the respective
|
|
146 |
kernels. For KVM no reboot should be necessary.
|
|
146 | 147 |
|
147 | 148 |
.. admonition:: Xen on Debian |
148 | 149 |
|
... | ... | |
315 | 316 |
You can use this command line to install all needed packages:: |
316 | 317 |
|
317 | 318 |
# apt-get install lvm2 ssh bridge-utils iproute iputils-arping \ |
318 |
python python-pyopenssl openssl python-pyparsing python-simplejson \
|
|
319 |
python-pyinotify |
|
319 |
python python-pyopenssl openssl python-pyparsing \ |
|
320 |
python-simplejson python-pyinotify
|
|
320 | 321 |
|
321 | 322 |
Setting up the environment for Ganeti |
322 | 323 |
------------------------------------- |
... | ... | |
326 | 327 |
|
327 | 328 |
**Mandatory** on all nodes. |
328 | 329 |
|
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. |
|
330 |
You can run Ganeti either in "bridge mode" or in "routed mode". In |
|
331 |
bridge mode, the default, the instances network interfaces will be |
|
332 |
attached to a software bridge running in dom0. Xen by default creates |
|
333 |
such a bridge at startup, but your distribution might have a different |
|
334 |
way to do things, and you'll definitely need to manually set it up under |
|
335 |
KVM. |
|
334 | 336 |
|
335 | 337 |
Beware that the default name Ganeti uses is ``xen-br0`` (which was |
336 | 338 |
used in Xen 2.0) while Xen 3.0 uses ``xenbr0`` by default. The default |
337 | 339 |
bridge your Ganeti cluster will use for new instances can be specified |
338 | 340 |
at cluster initialization time. |
339 | 341 |
|
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. |
|
342 |
If you want to run in "routing mode" you need to specify that at cluster |
|
343 |
init time (using the --nicparam option), and then no bridge will be |
|
344 |
needed. In this mode instance traffic will be routed by dom0, instead of |
|
345 |
bridged. |
|
343 | 346 |
|
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 |
In order to use "routing mode" under Xen, you'll need to change the |
|
348 |
relevant parameters in the Xen config file. Under KVM instead, no config |
|
349 |
change is necessary, but you still need to set up your network |
|
350 |
interfaces correctly. |
|
347 | 351 |
|
348 | 352 |
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. |
|
353 |
represent, if non-empty, a different routing table name or number to use |
|
354 |
for your instances. This allows insulation between different instance |
|
355 |
groups, and different routing policies between node traffic and instance |
|
356 |
traffic. |
|
352 | 357 |
|
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). |
|
358 |
You will need to configure your routing table basic routes and rules |
|
359 |
outside of ganeti. The vif scripts will only add /32 routes to your
|
|
360 |
instances, through their interface, in the table you specified (under
|
|
361 |
KVM, and in the main table under Xen).
|
|
357 | 362 |
|
358 | 363 |
.. admonition:: Bridging under Debian |
359 | 364 |
|
... | ... | |
512 | 517 |
**exclusively** for this purpose, and cannot be the name of the first |
513 | 518 |
(master) node. |
514 | 519 |
|
515 |
If you want to use a bridge which is not ``xen-br0``, or no bridge at all, use
|
|
516 |
the --nicparams
|
|
520 |
If you want to use a bridge which is not ``xen-br0``, or no bridge at |
|
521 |
all, use ``--nicparams``.
|
|
517 | 522 |
|
518 | 523 |
If the bridge name you are using is not ``xen-br0``, use the *-b |
519 | 524 |
<BRIDGENAME>* option to specify the bridge name. In this case, you |
Also available in: Unified diff