Revision 808753d4 doc/install.sgml
| b/doc/install.sgml | ||
|---|---|---|
| 314 | 314 |
</para> |
| 315 | 315 |
|
| 316 | 316 |
<para> |
| 317 |
Supported DRBD versions: the <literal>0.7</literal> series |
|
| 318 |
<emphasis role="strong">or</emphasis> |
|
| 319 |
<literal>8.0.7</literal>. It's recommended to have at least |
|
| 320 |
version <literal>0.7.24</literal> if you use |
|
| 321 |
<command>udev</command> since older versions have a bug |
|
| 322 |
related to device discovery which can be triggered in cases of |
|
| 323 |
hard drive failure. |
|
| 317 |
Supported DRBD versions: <literal>8.0.x</literal>. |
|
| 318 |
It's recommended to have at least version <literal>8.0.7</literal>. |
|
| 324 | 319 |
</para> |
| 325 | 320 |
|
| 326 | 321 |
<para> |
| ... | ... | |
| 336 | 331 |
you have the DRBD utils installed and the module in your |
| 337 | 332 |
kernel you're fine. Please check that your system is |
| 338 | 333 |
configured to load the module at every boot, and that it |
| 339 |
passes the following option to the module (for |
|
| 340 |
<literal>0.7.x</literal>: |
|
| 341 |
<computeroutput>minor_count=64</computeroutput> (this will |
|
| 342 |
allow you to use up to 32 instances per node) or for |
|
| 343 |
<literal>8.0.x</literal> you can use up to |
|
| 344 |
<constant>255</constant> |
|
| 345 |
(i.e. <computeroutput>minor_count=255</computeroutput>, but |
|
| 346 |
for most clusters <constant>128</constant> should be enough). |
|
| 334 |
passes the following option to the module |
|
| 335 |
<computeroutput>minor_count=255</computeroutput>. This will |
|
| 336 |
allow you to use up to 128 instances per node (for most clusters |
|
| 337 |
<constant>128 </constant> should be enough, though). |
|
| 347 | 338 |
</para> |
| 348 | 339 |
|
| 349 | 340 |
<formalpara><title>Debian</title> |
| 350 | 341 |
<para> |
| 351 |
You can just install (build) the DRBD 0.7 module with the
|
|
| 342 |
You can just install (build) the DRBD 8.0.x module with the
|
|
| 352 | 343 |
following commands (make sure you are running the Xen |
| 353 | 344 |
kernel): |
| 354 | 345 |
</para> |
| 355 | 346 |
</formalpara> |
| 356 | 347 |
|
| 357 | 348 |
<screen> |
| 358 |
apt-get install drbd0.7-module-source drbd0.7-utils |
|
| 359 |
m-a update |
|
| 360 |
m-a a-i drbd0.7 |
|
| 361 |
echo drbd minor_count=64 >> /etc/modules |
|
| 362 |
modprobe drbd minor_count=64 |
|
| 363 |
</screen> |
|
| 364 |
<para> |
|
| 365 |
or for using DRBD <literal>8.x</literal> from the etch |
|
| 366 |
backports (note: you need at least 8.0.7, older version have |
|
| 367 |
a bug that breaks ganeti's usage of drbd): |
|
| 368 |
</para> |
|
| 369 |
<screen> |
|
| 370 | 349 |
apt-get install -t etch-backports drbd8-module-source drbd8-utils |
| 371 | 350 |
m-a update |
| 372 | 351 |
m-a a-i drbd8 |
| ... | ... | |
| 376 | 355 |
|
| 377 | 356 |
<para> |
| 378 | 357 |
It is also recommended that you comment out the default |
| 379 |
resources in the <filename>/etc/dbrd.conf</filename> file, so
|
|
| 358 |
resources in the <filename>/etc/drbd.conf</filename> file, so
|
|
| 380 | 359 |
that the init script doesn't try to configure any drbd |
| 381 | 360 |
devices. You can do this by prefixing all |
| 382 | 361 |
<literal>resource</literal> lines in the file with the keyword |
| ... | ... | |
| 428 | 407 |
(part of iputils package)</simpara> |
| 429 | 408 |
</listitem> |
| 430 | 409 |
<listitem> |
| 431 |
<simpara><ulink |
|
| 432 |
url="http://www.kernel.org/pub/linux/utils/raid/mdadm/">mdadm</ulink> |
|
| 433 |
(Linux Software Raid tools)</simpara> |
|
| 434 |
</listitem> |
|
| 435 |
<listitem> |
|
| 436 | 410 |
<simpara><ulink url="http://www.python.org">Python 2.4</ulink></simpara> |
| 437 | 411 |
</listitem> |
| 438 | 412 |
<listitem> |
| 439 |
<simpara><ulink url="http://twistedmatrix.com/">Python |
|
| 440 |
Twisted library</ulink> - the core library is |
|
| 441 |
enough</simpara> |
|
| 442 |
</listitem> |
|
| 443 |
<listitem> |
|
| 444 | 413 |
<simpara><ulink |
| 445 | 414 |
url="http://pyopenssl.sourceforge.net/">Python OpenSSL |
| 446 | 415 |
bindings</ulink></simpara> |
| ... | ... | |
| 472 | 441 |
</formalpara> |
| 473 | 442 |
<screen> |
| 474 | 443 |
# apt-get install lvm2 ssh bridge-utils iproute iputils-arping \ |
| 475 |
python2.4 python-twisted-core python-pyopenssl openssl \ |
|
| 476 |
mdadm python-pyparsing python-simplejson |
|
| 444 |
python2.4 python-pyopenssl openssl python-pyparsing python-simplejson |
|
| 477 | 445 |
</screen> |
| 478 | 446 |
|
| 479 | 447 |
</sect2> |
| ... | ... | |
| 834 | 802 |
This step shows how to setup a virtual instance with either |
| 835 | 803 |
non-mirrored disks (<computeroutput>plain</computeroutput>) or |
| 836 | 804 |
with network mirrored disks |
| 837 |
(<computeroutput>remote_raid1</computeroutput> for drbd 0.7 |
|
| 838 |
and <computeroutput>drbd</computeroutput> for drbd 8.x). All |
|
| 805 |
(<computeroutput>drbd</computeroutput>). All |
|
| 839 | 806 |
commands need to be executed on the Ganeti master node (the |
| 840 | 807 |
one on which <computeroutput>gnt-cluster init</computeroutput> |
| 841 | 808 |
was run). Verify that the OS scripts are present on all |
| ... | ... | |
| 872 | 839 |
<para> |
| 873 | 840 |
To create a network mirrored instance, change the argument to |
| 874 | 841 |
the <option>-t</option> option from <literal>plain</literal> |
| 875 |
to <literal>remote_raid1</literal> (drbd 0.7) or |
|
| 876 |
<literal>drbd</literal> (drbd 8.0) and specify the node on |
|
| 842 |
to <literal>drbd</literal> and specify the node on |
|
| 877 | 843 |
which the mirror should reside with the second value of the |
| 878 | 844 |
<option>--node</option> option, like this: |
| 879 | 845 |
</para> |
| 880 | 846 |
|
| 881 | 847 |
<screen> |
| 882 |
# gnt-instance add -t remote_raid1 -n node1:node2 -o debian-etch instance2
|
|
| 848 |
# gnt-instance add -t drbd -n node1:node2 -o debian-etch instance2
|
|
| 883 | 849 |
* creating instance disks... |
| 884 | 850 |
adding instance instance2 to cluster config |
| 885 | 851 |
Waiting for instance instance1 to sync disks. |
| ... | ... | |
| 919 | 885 |
|
| 920 | 886 |
<para> |
| 921 | 887 |
To failover an instance to its secondary node (only possible |
| 922 |
in <literal>remote_raid1</literal> or <literal>drbd</literal>
|
|
| 923 |
disk templates), use <computeroutput>gnt-instance failover
|
|
| 888 |
with <literal>drbd</literal> disk templates), use
|
|
| 889 |
<computeroutput>gnt-instance failover |
|
| 924 | 890 |
<replaceable>INSTANCENAME</replaceable></computeroutput>. |
| 925 | 891 |
</para> |
| 926 | 892 |
|
Also available in: Unified diff