| 303 |
303 |
<sect2>
|
| 304 |
304 |
<title>Installing Ganeti</title>
|
| 305 |
305 |
|
| 306 |
|
<para>It's now time to install the Ganeti software itself if you
|
| 307 |
|
haven't done it yet. You can do it from source, with the usual
|
| 308 |
|
steps (note that the <option>localstatedir</option> options must
|
| 309 |
|
be set to <filename class="directory">/var</filename>):
|
|
306 |
<para>
|
|
307 |
It's now time to install the Ganeti software itself. You can
|
|
308 |
do it from source, with the usual steps (note that the
|
|
309 |
<option>localstatedir</option> options must be set to
|
|
310 |
<filename class="directory">/var</filename>):
|
|
311 |
</para>
|
| 310 |
312 |
|
| 311 |
313 |
<screen>
|
| 312 |
314 |
./configure --localstatedir=/var
|
| 313 |
315 |
make
|
| 314 |
316 |
make install
|
|
317 |
mkdir /srv/ganeti/ /srv/ganeti/os /srv/ganeti/export
|
| 315 |
318 |
</screen>
|
| 316 |
319 |
|
| 317 |
|
or you can install the package relevant to your distribution, for
|
| 318 |
|
example in Debian/Ubuntu:
|
| 319 |
|
|
| 320 |
|
<screen>
|
| 321 |
|
dpkg -i ganeti_VERSION_all.deb
|
| 322 |
|
</screen>
|
| 323 |
|
|
| 324 |
|
or, if you have a source repository that holds the Ganeti software:
|
| 325 |
|
|
| 326 |
|
<screen>
|
| 327 |
|
apt-get install ganeti
|
| 328 |
|
</screen>
|
|
320 |
<para>
|
|
321 |
You also need to copy from the source archive the file
|
|
322 |
<filename>docs/examples/ganeti.initd</filename> to
|
|
323 |
<filename>/etc/init.d/ganeti</filename> and register it into
|
|
324 |
your distribution's startup scripts, for example in Debian:
|
| 329 |
325 |
</para>
|
|
326 |
<screen>update-rc.d ganeti defaults 20 80</screen>
|
| 330 |
327 |
|
| 331 |
328 |
</sect2>
|
| 332 |
329 |
|
| ... | ... | |
| 369 |
366 |
</screen>
|
| 370 |
367 |
|
| 371 |
368 |
<para>
|
| 372 |
|
Options you can pass to <command>gnt-cluster init</command>
|
| 373 |
|
include the default bridge name (<option>-b</option>), the
|
| 374 |
|
cluster-wide name for the volume group (<option>-g</option>)
|
| 375 |
|
and the secondary ip address for the initial node should you
|
| 376 |
|
wish to keep the data replication network separate. Invoke it
|
| 377 |
|
with <option>--help</option> to see all the possibilities.
|
|
369 |
If the node's network interface which will be used for access
|
|
370 |
from outside the cluster is not named
|
|
371 |
<hardware>xen-br0</hardware>, you need to use the
|
|
372 |
<option>--master-netdev=<replaceable>IFNAME</replaceable></option>
|
|
373 |
option, replacing <replaceable>IFNAME</replaceable> with the
|
|
374 |
correct one for your case (e.g. <hardware>xenbr0</hardware>,
|
|
375 |
<hardware>eth0</hardware>, etc.). Usually this will be the
|
|
376 |
same as the default bridge name (see below).
|
|
377 |
</para>
|
|
378 |
|
|
379 |
<para>
|
|
380 |
Other options you can pass to <command>gnt-cluster
|
|
381 |
init</command> include the default bridge name
|
|
382 |
(<option>-b</option>), the cluster-wide name for the volume
|
|
383 |
group (<option>-g</option>) and the secondary ip address for
|
|
384 |
the initial node should you wish to keep the data replication
|
|
385 |
network separate. Invoke it with <option>--help</option> to
|
|
386 |
see all the possibilities.
|
| 378 |
387 |
</para>
|
| 379 |
388 |
|
| 380 |
389 |
<para>
|
| 381 |
390 |
Note that the cluster name must exist in DNS. You must choose
|
| 382 |
391 |
a name different from any of the nodes names for a multi-node
|
| 383 |
392 |
cluster. In general the best choice is to have a unique name
|
| 384 |
|
for a cluster, even if it consists of only one machine.
|
|
393 |
for a cluster, even if it consists of only one machine, as you
|
|
394 |
will be able to expand it later without any problem.
|
| 385 |
395 |
</para>
|
| 386 |
396 |
</sect2>
|
| 387 |
397 |
|