root / doc / install.rst @ e8a3bf18
History | View | Annotate | Download (23.6 kB)
1 |
Ganeti installation tutorial |
---|---|
2 |
============================ |
3 |
|
4 |
Documents Ganeti version |version| |
5 |
|
6 |
.. contents:: |
7 |
|
8 |
.. highlight:: text |
9 |
|
10 |
Introduction |
11 |
------------ |
12 |
|
13 |
Ganeti is a cluster virtualization management system based on Xen or |
14 |
KVM. This document explains how to bootstrap a Ganeti node (Xen *dom0*, |
15 |
the host Linux system for KVM), create a running cluster and install |
16 |
virtual instances (Xen *domUs*, KVM guests). You need to repeat most of |
17 |
the steps in this document for every node you want to install, but of |
18 |
course we recommend creating some semi-automatic procedure if you plan |
19 |
to deploy Ganeti on a medium/large scale. |
20 |
|
21 |
A basic Ganeti terminology glossary is provided in the introductory |
22 |
section of the :doc:`admin`. Please refer to that document if you are |
23 |
uncertain about the terms we are using. |
24 |
|
25 |
Ganeti has been developed for Linux and should be distribution-agnostic. |
26 |
This documentation will use Debian Lenny as an example system but the |
27 |
examples can be translated to any other distribution. You are expected |
28 |
to be familiar with your distribution, its package management system, |
29 |
and Xen or KVM before trying to use Ganeti. |
30 |
|
31 |
This document is divided into two main sections: |
32 |
|
33 |
- Installation of the base system and base components |
34 |
|
35 |
- Configuration of the environment for Ganeti |
36 |
|
37 |
Each of these is divided into sub-sections. While a full Ganeti system |
38 |
will need all of the steps specified, some are not strictly required for |
39 |
every environment. Which ones they are, and why, is specified in the |
40 |
corresponding sections. |
41 |
|
42 |
Installing the base system and base components |
43 |
---------------------------------------------- |
44 |
|
45 |
Hardware requirements |
46 |
+++++++++++++++++++++ |
47 |
|
48 |
Any system supported by your Linux distribution is fine. 64-bit systems |
49 |
are better as they can support more memory. |
50 |
|
51 |
Any disk drive recognized by Linux (``IDE``/``SCSI``/``SATA``/etc.) is |
52 |
supported in Ganeti. Note that no shared storage (e.g. ``SAN``) is |
53 |
needed to get high-availability features (but of course, one can be used |
54 |
to store the images). It is highly recommended to use more than one disk |
55 |
drive to improve speed. But Ganeti also works with one disk per machine. |
56 |
|
57 |
Installing the base system |
58 |
++++++++++++++++++++++++++ |
59 |
|
60 |
**Mandatory** on all nodes. |
61 |
|
62 |
It is advised to start with a clean, minimal install of the operating |
63 |
system. The only requirement you need to be aware of at this stage is to |
64 |
partition leaving enough space for a big (**minimum** 20GiB) LVM volume |
65 |
group which will then host your instance filesystems, if you want to use |
66 |
all Ganeti features. The volume group name Ganeti uses (by default) is |
67 |
``xenvg``. |
68 |
|
69 |
You can also use file-based storage only, without LVM, but this setup is |
70 |
not detailed in this document. |
71 |
|
72 |
While you can use an existing system, please note that the Ganeti |
73 |
installation is intrusive in terms of changes to the system |
74 |
configuration, and it's best to use a newly-installed system without |
75 |
important data on it. |
76 |
|
77 |
Also, for best results, it's advised that the nodes have as much as |
78 |
possible the same hardware and software configuration. This will make |
79 |
administration much easier. |
80 |
|
81 |
Hostname issues |
82 |
~~~~~~~~~~~~~~~ |
83 |
|
84 |
Note that Ganeti requires the hostnames of the systems (i.e. what the |
85 |
``hostname`` command outputs to be a fully-qualified name, not a short |
86 |
name. In other words, you should use *node1.example.com* as a hostname |
87 |
and not just *node1*. |
88 |
|
89 |
.. admonition:: Debian |
90 |
|
91 |
Debian Lenny and Etch configures the hostname differently than you |
92 |
need it for Ganeti. For example, this is what Etch puts in |
93 |
``/etc/hosts`` in certain situations:: |
94 |
|
95 |
127.0.0.1 localhost |
96 |
127.0.1.1 node1.example.com node1 |
97 |
|
98 |
but for Ganeti you need to have:: |
99 |
|
100 |
127.0.0.1 localhost |
101 |
192.168.1.1 node1.example.com node1 |
102 |
|
103 |
replacing ``192.168.1.1`` with your node's address. Also, the file |
104 |
``/etc/hostname`` which configures the hostname of the system |
105 |
should contain ``node1.example.com`` and not just ``node1`` (you |
106 |
need to run the command ``/etc/init.d/hostname.sh start`` after |
107 |
changing the file). |
108 |
|
109 |
.. admonition:: Why a fully qualified host name |
110 |
|
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. |
126 |
|
127 |
|
128 |
Installing The Hypervisor |
129 |
+++++++++++++++++++++++++ |
130 |
|
131 |
**Mandatory** on all nodes. |
132 |
|
133 |
While Ganeti is developed with the ability to modularly run on different |
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. |
137 |
|
138 |
Please follow your distribution's recommended way to install and set up |
139 |
Xen, or install Xen from the upstream source, if you wish, following |
140 |
their manual. For KVM, make sure you have a KVM-enabled kernel and the |
141 |
KVM tools. |
142 |
|
143 |
After installing Xen, you need to reboot into your new system. On some |
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. |
147 |
|
148 |
.. admonition:: Xen on Debian |
149 |
|
150 |
Under Lenny or Etch you can install the relevant ``xen-linux-system`` |
151 |
package, which will pull in both the hypervisor and the relevant |
152 |
kernel. Also, if you are installing a 32-bit Lenny/Etch, you should |
153 |
install the ``libc6-xen`` package (run ``apt-get install |
154 |
libc6-xen``). |
155 |
|
156 |
Xen settings |
157 |
~~~~~~~~~~~~ |
158 |
|
159 |
It's recommended that dom0 is restricted to a low amount of memory |
160 |
(512MiB or 1GiB is reasonable) and that memory ballooning is disabled in |
161 |
the file ``/etc/xen/xend-config.sxp`` by setting the value |
162 |
``dom0-min-mem`` to 0, like this:: |
163 |
|
164 |
(dom0-min-mem 0) |
165 |
|
166 |
For optimum performance when running both CPU and I/O intensive |
167 |
instances, it's also recommended that the dom0 is restricted to one CPU |
168 |
only, for example by booting with the kernel parameter ``nosmp``. |
169 |
|
170 |
It is recommended that you disable xen's automatic save of virtual |
171 |
machines at system shutdown and subsequent restore of them at reboot. |
172 |
To obtain this make sure the variable ``XENDOMAINS_SAVE`` in the file |
173 |
``/etc/default/xendomains`` is set to an empty value. |
174 |
|
175 |
If you want to use live migration make sure you have, in the xen config |
176 |
file, something that allows the nodes to migrate instances between each |
177 |
other. For example:: |
178 |
|
179 |
(xend-relocation-server yes) |
180 |
(xend-relocation-port 8002) |
181 |
(xend-relocation-address '') |
182 |
(xend-relocation-hosts-allow '^192\\.168\\.3\\.[0-9]+$') |
183 |
|
184 |
|
185 |
The second line assumess that the hypervisor parameter |
186 |
``migration_port`` is set 8002, otherwise modify it to match. The last |
187 |
line assumes that all your nodes have secondary IPs in the |
188 |
192.168.3.0/24 network, adjust it accordingly to your setup. |
189 |
|
190 |
.. admonition:: Debian |
191 |
|
192 |
Besides the ballooning change which you need to set in |
193 |
``/etc/xen/xend-config.sxp``, you need to set the memory and nosmp |
194 |
parameters in the file ``/boot/grub/menu.lst``. You need to modify |
195 |
the variable ``xenhopt`` to add ``dom0_mem=1024M`` like this:: |
196 |
|
197 |
## Xen hypervisor options to use with the default Xen boot option |
198 |
# xenhopt=dom0_mem=1024M |
199 |
|
200 |
and the ``xenkopt`` needs to include the ``nosmp`` option like this:: |
201 |
|
202 |
## Xen Linux kernel options to use with the default Xen boot option |
203 |
# xenkopt=nosmp |
204 |
|
205 |
Any existing parameters can be left in place: it's ok to have |
206 |
``xenkopt=console=tty0 nosmp``, for example. After modifying the |
207 |
files, you need to run:: |
208 |
|
209 |
/sbin/update-grub |
210 |
|
211 |
If you want to run HVM instances too with Ganeti and want VNC access to |
212 |
the console of your instances, set the following two entries in |
213 |
``/etc/xen/xend-config.sxp``:: |
214 |
|
215 |
(vnc-listen '0.0.0.0') (vncpasswd '') |
216 |
|
217 |
You need to restart the Xen daemon for these settings to take effect:: |
218 |
|
219 |
/etc/init.d/xend restart |
220 |
|
221 |
Selecting the instance kernel |
222 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
223 |
|
224 |
After you have installed Xen, you need to tell Ganeti exactly what |
225 |
kernel to use for the instances it will create. This is done by creating |
226 |
a symlink from your actual kernel to ``/boot/vmlinuz-2.6-xenU``, and one |
227 |
from your initrd to ``/boot/initrd-2.6-xenU`` [#defkernel]_. Note that |
228 |
if you don't use an initrd for the domU kernel, you don't need to create |
229 |
the initrd symlink. |
230 |
|
231 |
.. admonition:: Debian |
232 |
|
233 |
After installation of the ``xen-linux-system`` package, you need to |
234 |
run (replace the exact version number with the one you have):: |
235 |
|
236 |
cd /boot |
237 |
ln -s vmlinuz-2.6.26-1-xen-amd64 vmlinuz-2.6-xenU |
238 |
ln -s initrd.img-2.6.26-1-xen-amd64 initrd-2.6-xenU |
239 |
|
240 |
Installing DRBD |
241 |
+++++++++++++++ |
242 |
|
243 |
Recommended on all nodes: DRBD_ is required if you want to use the high |
244 |
availability (HA) features of Ganeti, but optional if you don't require |
245 |
them or only run Ganeti on single-node clusters. You can upgrade a |
246 |
non-HA cluster to an HA one later, but you might need to export and |
247 |
re-import all your instances to take advantage of the new features. |
248 |
|
249 |
.. _DRBD: http://www.drbd.org/ |
250 |
|
251 |
Supported DRBD versions: 8.0+. It's recommended to have at least version |
252 |
8.0.12. Note that for version 8.2 and newer it is needed to pass the |
253 |
``usermode_helper=/bin/true`` parameter to the module, either by |
254 |
configuring ``/etc/modules`` or when inserting it manually. |
255 |
|
256 |
Now the bad news: unless your distribution already provides it |
257 |
installing DRBD might involve recompiling your kernel or anyway fiddling |
258 |
with it. Hopefully at least the Xen-ified kernel source to start from |
259 |
will be provided (if you intend to use Xen). |
260 |
|
261 |
The good news is that you don't need to configure DRBD at all. Ganeti |
262 |
will do it for you for every instance you set up. If you have the DRBD |
263 |
utils installed and the module in your kernel you're fine. Please check |
264 |
that your system is configured to load the module at every boot, and |
265 |
that it passes the following option to the module: |
266 |
``minor_count=NUMBER``. We recommend that you use 128 as the value of |
267 |
the minor_count - this will allow you to use up to 64 instances in total |
268 |
per node (both primary and secondary, when using only one disk per |
269 |
instance). You can increase the number up to 255 if you need more |
270 |
instances on a node. |
271 |
|
272 |
|
273 |
.. admonition:: Debian |
274 |
|
275 |
On Debian, you can just install (build) the DRBD module with the |
276 |
following commands, making sure you are running the target (Xen or |
277 |
KVM) kernel:: |
278 |
|
279 |
apt-get install drbd8-source drbd8-utils |
280 |
m-a update |
281 |
m-a a-i drbd8 |
282 |
echo drbd minor_count=128 usermode_helper=/bin/true >> /etc/modules |
283 |
depmod -a |
284 |
modprobe drbd minor_count=128 usermode_helper=/bin/true |
285 |
|
286 |
It is also recommended that you comment out the default resources in |
287 |
the ``/etc/drbd.conf`` file, so that the init script doesn't try to |
288 |
configure any drbd devices. You can do this by prefixing all |
289 |
*resource* lines in the file with the keyword *skip*, like this:: |
290 |
|
291 |
skip resource r0 { |
292 |
... |
293 |
} |
294 |
|
295 |
skip resource "r1" { |
296 |
... |
297 |
} |
298 |
|
299 |
Other required software |
300 |
+++++++++++++++++++++++ |
301 |
|
302 |
Besides Xen and DRBD, you will need to install the following (on all |
303 |
nodes): |
304 |
|
305 |
- LVM version 2, `<http://sourceware.org/lvm2/>`_ |
306 |
|
307 |
- OpenSSL, `<http://www.openssl.org/>`_ |
308 |
|
309 |
- OpenSSH, `<http://www.openssh.com/portable.html>`_ |
310 |
|
311 |
- bridge utilities, `<http://bridge.sourceforge.net/>`_ |
312 |
|
313 |
- iproute2, `<http://developer.osdl.org/dev/iproute2>`_ |
314 |
|
315 |
- arping (part of iputils package), |
316 |
`<ftp://ftp.inr.ac.ru/ip-routing/iputils-current.tar.gz>`_ |
317 |
|
318 |
- Python version 2.4 or 2.5, `<http://www.python.org>`_ |
319 |
|
320 |
- Python OpenSSL bindings, `<http://pyopenssl.sourceforge.net/>`_ |
321 |
|
322 |
- simplejson Python module, `<http://www.undefined.org/python/#simplejson>`_ |
323 |
|
324 |
- pyparsing Python module, `<http://pyparsing.wikispaces.com/>`_ |
325 |
|
326 |
- pyinotify Python module, `<http://trac.dbzteam.org/pyinotify>`_ |
327 |
|
328 |
These programs are supplied as part of most Linux distributions, so |
329 |
usually they can be installed via apt or similar methods. Also many of |
330 |
them will already be installed on a standard machine. |
331 |
|
332 |
|
333 |
.. admonition:: Debian |
334 |
|
335 |
You can use this command line to install all needed packages:: |
336 |
|
337 |
# apt-get install lvm2 ssh bridge-utils iproute iputils-arping \ |
338 |
python python-pyopenssl openssl python-pyparsing \ |
339 |
python-simplejson python-pyinotify |
340 |
|
341 |
Setting up the environment for Ganeti |
342 |
------------------------------------- |
343 |
|
344 |
Configuring the network |
345 |
+++++++++++++++++++++++ |
346 |
|
347 |
**Mandatory** on all nodes. |
348 |
|
349 |
You can run Ganeti either in "bridge mode" or in "routed mode". In |
350 |
bridge mode, the default, the instances network interfaces will be |
351 |
attached to a software bridge running in dom0. Xen by default creates |
352 |
such a bridge at startup, but your distribution might have a different |
353 |
way to do things, and you'll definitely need to manually set it up under |
354 |
KVM. |
355 |
|
356 |
Beware that the default name Ganeti uses is ``xen-br0`` (which was used |
357 |
in Xen 2.0) while Xen 3.0 uses ``xenbr0`` by default. The default bridge |
358 |
your Ganeti cluster will use for new instances can be specified at |
359 |
cluster initialization time. |
360 |
|
361 |
If you want to run in "routing mode" you need to specify that at cluster |
362 |
init time (using the --nicparam option), and then no bridge will be |
363 |
needed. In this mode instance traffic will be routed by dom0, instead of |
364 |
bridged. |
365 |
|
366 |
In order to use "routing mode" under Xen, you'll need to change the |
367 |
relevant parameters in the Xen config file. Under KVM instead, no config |
368 |
change is necessary, but you still need to set up your network |
369 |
interfaces correctly. |
370 |
|
371 |
By default, under KVM, the "link" parameter you specify per-nic will |
372 |
represent, if non-empty, a different routing table name or number to use |
373 |
for your instances. This allows insulation between different instance |
374 |
groups, and different routing policies between node traffic and instance |
375 |
traffic. |
376 |
|
377 |
You will need to configure your routing table basic routes and rules |
378 |
outside of ganeti. The vif scripts will only add /32 routes to your |
379 |
instances, through their interface, in the table you specified (under |
380 |
KVM, and in the main table under Xen). |
381 |
|
382 |
.. admonition:: Bridging under Debian |
383 |
|
384 |
The recommended way to configure the Xen bridge is to edit your |
385 |
``/etc/network/interfaces`` file and substitute your normal |
386 |
Ethernet stanza with the following snippet:: |
387 |
|
388 |
auto xen-br0 |
389 |
iface xen-br0 inet static |
390 |
address YOUR_IP_ADDRESS |
391 |
netmask YOUR_NETMASK |
392 |
network YOUR_NETWORK |
393 |
broadcast YOUR_BROADCAST_ADDRESS |
394 |
gateway YOUR_GATEWAY |
395 |
bridge_ports eth0 |
396 |
bridge_stp off |
397 |
bridge_fd 0 |
398 |
|
399 |
The following commands need to be executed on the local console: |
400 |
|
401 |
ifdown eth0 |
402 |
ifup xen-br0 |
403 |
|
404 |
To check if the bridge is setup, use the ``ip`` and ``brctl show`` |
405 |
commands:: |
406 |
|
407 |
# ip a show xen-br0 |
408 |
9: xen-br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue |
409 |
link/ether 00:20:fc:1e:d5:5d brd ff:ff:ff:ff:ff:ff |
410 |
inet 10.1.1.200/24 brd 10.1.1.255 scope global xen-br0 |
411 |
inet6 fe80::220:fcff:fe1e:d55d/64 scope link |
412 |
valid_lft forever preferred_lft forever |
413 |
|
414 |
# brctl show xen-br0 |
415 |
bridge name bridge id STP enabled interfaces |
416 |
xen-br0 8000.0020fc1ed55d no eth0 |
417 |
|
418 |
.. _configure-lvm-label: |
419 |
|
420 |
Configuring LVM |
421 |
+++++++++++++++ |
422 |
|
423 |
**Mandatory** on all nodes. |
424 |
|
425 |
The volume group is required to be at least 20GiB. |
426 |
|
427 |
If you haven't configured your LVM volume group at install time you need |
428 |
to do it before trying to initialize the Ganeti cluster. This is done by |
429 |
formatting the devices/partitions you want to use for it and then adding |
430 |
them to the relevant volume group:: |
431 |
|
432 |
pvcreate /dev/sda3 |
433 |
vgcreate xenvg /dev/sda3 |
434 |
|
435 |
or:: |
436 |
|
437 |
pvcreate /dev/sdb1 |
438 |
pvcreate /dev/sdc1 |
439 |
vgcreate xenvg /dev/sdb1 /dev/sdc1 |
440 |
|
441 |
If you want to add a device later you can do so with the *vgextend* |
442 |
command:: |
443 |
|
444 |
pvcreate /dev/sdd1 |
445 |
vgextend xenvg /dev/sdd1 |
446 |
|
447 |
Optional: it is recommended to configure LVM not to scan the DRBD |
448 |
devices for physical volumes. This can be accomplished by editing |
449 |
``/etc/lvm/lvm.conf`` and adding the ``/dev/drbd[0-9]+`` regular |
450 |
expression to the ``filter`` variable, like this:: |
451 |
|
452 |
filter = ["r|/dev/cdrom|", "r|/dev/drbd[0-9]+|" ] |
453 |
|
454 |
Note that with Ganeti a helper script is provided - ``lvmstrap`` which |
455 |
will erase and configure as LVM any not in-use disk on your system. This |
456 |
is dangerous and it's recommended to read its ``--help`` output if you |
457 |
want to use it. |
458 |
|
459 |
Installing Ganeti |
460 |
+++++++++++++++++ |
461 |
|
462 |
**Mandatory** on all nodes. |
463 |
|
464 |
It's now time to install the Ganeti software itself. Download the |
465 |
source from the project page at `<http://code.google.com/p/ganeti/>`_, |
466 |
and install it (replace 2.0.0 with the latest version):: |
467 |
|
468 |
tar xvzf ganeti-2.0.0.tar.gz |
469 |
cd ganeti-2.0.0 |
470 |
./configure --localstatedir=/var --sysconfdir=/etc |
471 |
make |
472 |
make install |
473 |
mkdir /srv/ganeti/ /srv/ganeti/os /srv/ganeti/export |
474 |
|
475 |
You also need to copy the file ``doc/examples/ganeti.initd`` from the |
476 |
source archive to ``/etc/init.d/ganeti`` and register it with your |
477 |
distribution's startup scripts, for example in Debian:: |
478 |
|
479 |
update-rc.d ganeti defaults 20 80 |
480 |
|
481 |
In order to automatically restart failed instances, you need to setup a |
482 |
cron job run the *ganeti-watcher* command. A sample cron file is |
483 |
provided in the source at ``doc/examples/ganeti.cron`` and you can copy |
484 |
that (eventually altering the path) to ``/etc/cron.d/ganeti``. |
485 |
|
486 |
What gets installed |
487 |
~~~~~~~~~~~~~~~~~~~ |
488 |
|
489 |
The above ``make install`` invocation, or installing via your |
490 |
distribution mechanisms, will install on the system: |
491 |
|
492 |
- a set of python libraries under the *ganeti* namespace (depending on |
493 |
the python version this can be located in either |
494 |
``lib/python-$ver/site-packages`` or various other locations) |
495 |
- a set of programs under ``/usr/local/sbin`` or ``/usr/sbin`` |
496 |
- man pages for the above programs |
497 |
- a set of tools under the ``lib/ganeti/tools`` directory |
498 |
- an example iallocator script (see the admin guide for details) under |
499 |
``lib/ganeti/iallocators`` |
500 |
- a cron job that is needed for cluster maintenance |
501 |
- an init script for automatic startup of Ganeti daemons |
502 |
- provided but not installed automatically by ``make install`` is a bash |
503 |
completion script that hopefully will ease working with the many |
504 |
cluster commands |
505 |
|
506 |
Installing the Operating System support packages |
507 |
++++++++++++++++++++++++++++++++++++++++++++++++ |
508 |
|
509 |
**Mandatory** on all nodes. |
510 |
|
511 |
To be able to install instances you need to have an Operating System |
512 |
installation script. An example OS that works under Debian and can |
513 |
install Debian and Ubuntu instace OSes is provided on the project web |
514 |
site. Download it from the project page and follow the instructions in |
515 |
the ``README`` file. Here is the installation procedure (replace 0.7 |
516 |
with the latest version that is compatible with your ganeti version):: |
517 |
|
518 |
cd /usr/local/src/ |
519 |
wget http://ganeti.googlecode.com/files/ganeti-instance-debootstrap-0.7.tar.gz |
520 |
tar xzf ganeti-instance-debootstrap-0.7.tar.gz |
521 |
cd ganeti-instance-debootstrap-0.7 |
522 |
./configure |
523 |
make |
524 |
make install |
525 |
|
526 |
In order to use this OS definition, you need to have internet access |
527 |
from your nodes and have the *debootstrap*, *dump* and *restore* |
528 |
commands installed on all nodes. Also, if the OS is configured to |
529 |
partition the instance's disk in |
530 |
``/etc/default/ganeti-instance-debootstrap``, you will need *kpartx* |
531 |
installed. |
532 |
|
533 |
.. admonition:: Debian |
534 |
|
535 |
Use this command on all nodes to install the required packages:: |
536 |
|
537 |
apt-get install debootstrap dump kpartx |
538 |
|
539 |
Alternatively, you can create your own OS definitions. See the manpage |
540 |
:manpage:`ganeti-os-interface`. |
541 |
|
542 |
Initializing the cluster |
543 |
++++++++++++++++++++++++ |
544 |
|
545 |
**Mandatory** once per cluster, on the first node. |
546 |
|
547 |
The last step is to initialize the cluster. After you have repeated the |
548 |
above process on all of your nodes, choose one as the master, and |
549 |
execute:: |
550 |
|
551 |
gnt-cluster init <CLUSTERNAME> |
552 |
|
553 |
The *CLUSTERNAME* is a hostname, which must be resolvable (e.g. it must |
554 |
exist in DNS or in ``/etc/hosts``) by all the nodes in the cluster. You |
555 |
must choose a name different from any of the nodes names for a |
556 |
multi-node cluster. In general the best choice is to have a unique name |
557 |
for a cluster, even if it consists of only one machine, as you will be |
558 |
able to expand it later without any problems. Please note that the |
559 |
hostname used for this must resolve to an IP address reserved |
560 |
**exclusively** for this purpose, and cannot be the name of the first |
561 |
(master) node. |
562 |
|
563 |
If you want to use a bridge which is not ``xen-br0``, or no bridge at |
564 |
all, use ``--nicparams``. |
565 |
|
566 |
If the bridge name you are using is not ``xen-br0``, use the *-b |
567 |
<BRIDGENAME>* option to specify the bridge name. In this case, you |
568 |
should also use the *--master-netdev <BRIDGENAME>* option with the same |
569 |
BRIDGENAME argument. |
570 |
|
571 |
You can use a different name than ``xenvg`` for the volume group (but |
572 |
note that the name must be identical on all nodes). In this case you |
573 |
need to specify it by passing the *-g <VGNAME>* option to ``gnt-cluster |
574 |
init``. |
575 |
|
576 |
To set up the cluster as an Xen HVM cluster, use the |
577 |
``--enabled-hypervisors=xen-hvm`` option to enable the HVM hypervisor |
578 |
(you can also add ``,xen-pvm`` to enable the PVM one too). You will also |
579 |
need to create the VNC cluster password file |
580 |
``/etc/ganeti/vnc-cluster-password`` which contains one line with the |
581 |
default VNC password for the cluster. |
582 |
|
583 |
To setup the cluster for KVM-only usage (KVM and Xen cannot be mixed), |
584 |
pass ``--enabled-hypervisors=kvm`` to the init command. |
585 |
|
586 |
You can also invoke the command with the ``--help`` option in order to |
587 |
see all the possibilities. |
588 |
|
589 |
Joining the nodes to the cluster |
590 |
++++++++++++++++++++++++++++++++ |
591 |
|
592 |
**Mandatory** for all the other nodes. |
593 |
|
594 |
After you have initialized your cluster you need to join the other nodes |
595 |
to it. You can do so by executing the following command on the master |
596 |
node:: |
597 |
|
598 |
gnt-node add <NODENAME> |
599 |
|
600 |
Separate replication network |
601 |
++++++++++++++++++++++++++++ |
602 |
|
603 |
**Optional** |
604 |
|
605 |
Ganeti uses DRBD to mirror the disk of the virtual instances between |
606 |
nodes. To use a dedicated network interface for this (in order to |
607 |
improve performance or to enhance security) you need to configure an |
608 |
additional interface for each node. Use the *-s* option with |
609 |
``gnt-cluster init`` and ``gnt-node add`` to specify the IP address of |
610 |
this secondary interface to use for each node. Note that if you |
611 |
specified this option at cluster setup time, you must afterwards use it |
612 |
for every node add operation. |
613 |
|
614 |
Testing the setup |
615 |
+++++++++++++++++ |
616 |
|
617 |
Execute the ``gnt-node list`` command to see all nodes in the cluster:: |
618 |
|
619 |
# gnt-node list |
620 |
Node DTotal DFree MTotal MNode MFree Pinst Sinst |
621 |
node1.example.com 197404 197404 2047 1896 125 0 0 |
622 |
|
623 |
The above shows a couple of things: |
624 |
|
625 |
- The various Ganeti daemons can talk to each other |
626 |
- Ganeti can examine the storage of the node (DTotal/DFree) |
627 |
- Ganeti can talk to the selected hypervisor (MTotal/MNode/MFree) |
628 |
|
629 |
Cluster burnin |
630 |
~~~~~~~~~~~~~~ |
631 |
|
632 |
With Ganeti a tool called :command:`burnin` is provided that can test |
633 |
most of the Ganeti functionality. The tool is installed under the |
634 |
``lib/ganeti/tools`` directory (either under ``/usr`` or ``/usr/local`` |
635 |
based on the installation method). See more details under |
636 |
:ref:`burnin-label`. |
637 |
|
638 |
Further steps |
639 |
------------- |
640 |
|
641 |
You can now proceed either to the :doc:`admin`, or read the manpages of |
642 |
the various commands (:manpage:`ganeti(7)`, :manpage:`gnt-cluster(8)`, |
643 |
:manpage:`gnt-node(8)`, :manpage:`gnt-instance(8)`, |
644 |
:manpage:`gnt-job(8)`). |
645 |
|
646 |
.. rubric:: Footnotes |
647 |
|
648 |
.. [#defkernel] The kernel and initrd paths can be changed at either |
649 |
cluster level (which changes the default for all instances) or at |
650 |
instance level. |
651 |
|
652 |
.. vim: set textwidth=72 : |
653 |
.. Local Variables: |
654 |
.. mode: rst |
655 |
.. fill-column: 72 |
656 |
.. End: |