Revision bd028152
b/INSTALL | ||
---|---|---|
12 | 12 |
Before installing, please verify that you have the following programs: |
13 | 13 |
- Xen virtualization (version 3.0.x or 3.1) |
14 | 14 |
http://xen.xensource.com/ |
15 |
- DRBD (kernel module and userspace utils), version 0.7.x or 8.0.7+
|
|
15 |
- DRBD (kernel module and userspace utils), version 8.0.7+ |
|
16 | 16 |
http://www.drbd.org/ |
17 | 17 |
- LVM2 |
18 | 18 |
http://sourceware.org/lvm2/ |
... | ... | |
26 | 26 |
http://developer.osdl.org/dev/iproute2 |
27 | 27 |
- arping (part of iputils package) |
28 | 28 |
ftp://ftp.inr.ac.ru/ip-routing/iputils-current.tar.gz |
29 |
- mdadm (Linux Software Raid tools) (needed only with drbd 0.7.x) |
|
30 |
http://www.kernel.org/pub/linux/utils/raid/mdadm/ |
|
31 | 29 |
- Python 2.4 |
32 | 30 |
http://www.python.org |
33 | 31 |
- Python Twisted library (the core is enough) |
b/SECURITY | ||
---|---|---|
5 | 5 |
security model is all-or-nothing. |
6 | 6 |
|
7 | 7 |
All the Ganeti code runs as root, because all the operations that Ganeti |
8 |
is doing require privileges: creating logical volumes, md arrays,
|
|
8 |
is doing require privileges: creating logical volumes, drbd devices,
|
|
9 | 9 |
starting instances, etc. Running as root does not mean setuid, but that |
10 | 10 |
you need to be root to run the cluster commands. |
11 | 11 |
|
... | ... | |
39 | 39 |
Note that only the ssh key will allow other machines to run random |
40 | 40 |
commands on this node; the RPC method will run only: |
41 | 41 |
- well defined commands to create, remove, activate logical volumes, |
42 |
DRBD disks, md arrays, start/stop instances, etc;
|
|
42 |
drbd devices, start/stop instances, etc;
|
|
43 | 43 |
- run ssh commands on other nodes in the cluster, again well-defined |
44 | 44 |
- scripts under the /etc/ganeti/hooks directory |
45 | 45 |
|
b/man/gnt-backup.sgml | ||
---|---|---|
104 | 104 |
<arg choice="req">-t<group> |
105 | 105 |
<arg>diskless</arg> |
106 | 106 |
<arg>plain</arg> |
107 |
<arg>local_raid1</arg> |
|
108 |
<arg>remote_raid1</arg> |
|
109 | 107 |
<arg>drbd</arg> |
110 | 108 |
</group></arg> |
111 | 109 |
<sbr> |
... | ... | |
173 | 171 |
</listitem> |
174 | 172 |
</varlistentry> |
175 | 173 |
<varlistentry> |
176 |
<term>local_raid1</term> |
|
177 |
<listitem> |
|
178 |
<para> |
|
179 |
Disk devices will be md raid1 arrays over two local |
|
180 |
logical volumes. |
|
181 |
</para> |
|
182 |
</listitem> |
|
183 |
</varlistentry> |
|
184 |
<varlistentry> |
|
185 |
<term>remote_raid1</term> |
|
186 |
<listitem> |
|
187 |
<para> |
|
188 |
Disk devices will be md raid1 arrays with one |
|
189 |
component (so it's not actually raid1): a drbd (0.7.x) |
|
190 |
device between the instance's primary node and the |
|
191 |
node given by the second value of the |
|
192 |
<option>--node</option> option. |
|
193 |
</para> |
|
194 |
</listitem> |
|
195 |
</varlistentry> |
|
196 |
<varlistentry> |
|
197 | 174 |
<term>drbd</term> |
198 | 175 |
<listitem> |
199 | 176 |
<para> |
200 | 177 |
Disk devices will be drbd (version 8.x) on top of lvm |
201 |
volumes. They are equivalent in functionality to |
|
202 |
<replaceable>remote_raid1</replaceable>, but are |
|
203 |
recommended for new instances (if you have drbd 8.x |
|
204 |
installed). |
|
178 |
volumes. |
|
205 | 179 |
</para> |
206 | 180 |
</listitem> |
207 | 181 |
</varlistentry> |
... | ... | |
209 | 183 |
</para> |
210 | 184 |
|
211 | 185 |
<para> |
212 |
The optional second value of the <option>--node</option> is used for
|
|
213 |
the remote raid template type and specifies the remote node.
|
|
186 |
The optional second value of the <option>--node</option> is |
|
187 |
used for the drbd disk template and specifies the remote node.
|
|
214 | 188 |
</para> |
215 | 189 |
|
216 | 190 |
<para> |
b/man/gnt-instance.sgml | ||
---|---|---|
270 | 270 |
|
271 | 271 |
<para> |
272 | 272 |
The optional second value of the <option>--node</option> is used for |
273 |
the remote raid template type and specifies the remote node.
|
|
273 |
the drbd template type and specifies the remote node.
|
|
274 | 274 |
</para> |
275 | 275 |
|
276 | 276 |
<para> |
... | ... | |
327 | 327 |
interface has the advantage of better performance. Especially |
328 | 328 |
if you use a network file system (e.g. NFS) to store your instances |
329 | 329 |
this is the recommended choice. |
330 |
</para>
|
|
330 |
</para> |
|
331 | 331 |
|
332 | 332 |
<para> |
333 | 333 |
Example: |
... | ... | |
569 | 569 |
Show detailed information about the (given) instances. This |
570 | 570 |
is different from <command>list</command> as it shows |
571 | 571 |
detailed data about the instance's disks (especially useful |
572 |
for remote raid templates).
|
|
572 |
for drbd disk template).
|
|
573 | 573 |
</para> |
574 | 574 |
</refsect3> |
575 | 575 |
|
... | ... | |
907 | 907 |
|
908 | 908 |
<cmdsynopsis> |
909 | 909 |
<command>replace-disks</command> |
910 |
<arg choice="opt">--new-secondary <replaceable>NODE</replaceable></arg> |
|
911 |
<arg choice="req"><replaceable>instance</replaceable></arg> |
|
912 |
</cmdsynopsis> |
|
913 |
|
|
914 |
<cmdsynopsis> |
|
915 |
<command>replace-disks</command> |
|
916 | 910 |
<arg choice="opt">-s</arg> |
917 | 911 |
<arg choice="req">--new-secondary <replaceable>NODE</replaceable></arg> |
918 | 912 |
<arg choice="req"><replaceable>instance</replaceable></arg> |
... | ... | |
929 | 923 |
|
930 | 924 |
<para> |
931 | 925 |
This command is a generalized form for adding and replacing |
932 |
disks. |
|
933 |
</para> |
|
934 |
|
|
935 |
<para> |
|
936 |
The first form is usable with the |
|
937 |
<literal>remote_raid1</literal> disk template. This will |
|
938 |
replace the disks on both the primary and secondary node, |
|
939 |
and optionally will change the secondary node to a new one |
|
940 |
if you pass the <option>--new-secondary</option> option. |
|
926 |
disks. It is currently only valid for the mirrored (DRBD) |
|
927 |
disk template. |
|
941 | 928 |
</para> |
942 | 929 |
|
943 | 930 |
<para> |
944 |
The second and third forms are usable with the |
|
945 |
<literal>drbd</literal> disk template. The second form will |
|
946 |
do a secondary replacement, but as opposed to the |
|
947 |
<literal>remote_raid1</literal> will not replace the disks |
|
948 |
on the primary, therefore it will execute faster. The third |
|
949 |
form will replace the disks on either the primary |
|
931 |
The first form will do a secondary node change, while the |
|
932 |
second form will replace the disks on either the primary |
|
950 | 933 |
(<option>-p</option>) or the secondary (<option>-s</option>) |
951 | 934 |
node of the instance only, without changing the node. |
952 | 935 |
</para> |
... | ... | |
965 | 948 |
successful, the command will show the location and name of |
966 | 949 |
the block devices: |
967 | 950 |
<screen> |
968 |
node1.example.com:sda:/dev/md0
|
|
969 |
node1.example.com:sdb:/dev/md1
|
|
951 |
node1.example.com:sda:/dev/drbd0
|
|
952 |
node1.example.com:sdb:/dev/drbd1
|
|
970 | 953 |
</screen> |
971 | 954 |
|
972 | 955 |
In this example, <emphasis>node1.example.com</emphasis> is |
973 | 956 |
the name of the node on which the devices have been |
974 | 957 |
activated. The <emphasis>sda</emphasis> and |
975 | 958 |
<emphasis>sdb</emphasis> are the names of the block devices |
976 |
inside the instance. <emphasis>/dev/md0</emphasis> and
|
|
977 |
<emphasis>/dev/md1</emphasis> are the names of the block
|
|
959 |
inside the instance. <emphasis>/dev/drbd0</emphasis> and
|
|
960 |
<emphasis>/dev/drbd1</emphasis> are the names of the block
|
|
978 | 961 |
devices as visible on the node. |
979 | 962 |
</para> |
980 | 963 |
|
... | ... | |
993 | 976 |
</cmdsynopsis> |
994 | 977 |
<para> |
995 | 978 |
De-activates the block devices of the given instance. Note |
996 |
that if you run this command for a remote raid instance
|
|
997 |
type, while it is running, it will not be able to shutdown
|
|
998 |
the block devices on the primary node, but it will shutdown
|
|
999 |
the block devices on the secondary nodes, thus breaking the
|
|
1000 |
replication. |
|
979 |
that if you run this command for an instance with a drbd
|
|
980 |
disk template, while it is running, it will not be able to
|
|
981 |
shutdown the block devices on the primary node, but it will
|
|
982 |
shutdown the block devices on the secondary nodes, thus
|
|
983 |
breaking the replication.
|
|
1001 | 984 |
</para> |
1002 | 985 |
|
1003 | 986 |
</refsect3> |
... | ... | |
1019 | 1002 |
|
1020 | 1003 |
<para> |
1021 | 1004 |
Failover will fail the instance over its secondary |
1022 |
node. This works only for instances having a remote raid
|
|
1023 |
disk layout.
|
|
1005 |
node. This works only for instances having a drbd disk
|
|
1006 |
template.
|
|
1024 | 1007 |
</para> |
1025 | 1008 |
|
1026 | 1009 |
<para> |
b/man/gnt-node.sgml | ||
---|---|---|
146 | 146 |
This command will change the secondary node from the source |
147 | 147 |
node to the destination node for all instances having the |
148 | 148 |
source node as secondary. It works only for instances having |
149 |
a remote_raid1 or drbd disk layout.
|
|
149 |
a drbd disk template.
|
|
150 | 150 |
</para> |
151 | 151 |
|
152 | 152 |
<para> |
... | ... | |
170 | 170 |
<para> |
171 | 171 |
This command will fail over all instances having the given |
172 | 172 |
node as primary to their secondary nodes. This works only for |
173 |
instances having a remote raid disk layout.
|
|
173 |
instances having a drbd disk template.
|
|
174 | 174 |
</para> |
175 | 175 |
|
176 | 176 |
<para> |
Also available in: Unified diff