Revision 53b78ba4

b/docs/admin.sgml
130 130
	  want to use the default one</simpara>
131 131
        </listitem>
132 132
      </itemizedlist>
133
      If you want to create an highly available instance use the remote_raid1
134
      disk template:
133
      </para>
134

  
135
      <para>There are four types of disk template you can choose from:
136

  
137
      <variablelist>
138
        <varlistentry>
139
          <term>diskless</term>
140
	  <listitem><para>The instance has no disks. Only used for special
141
	  purpouse operating systems or for testing.</para></listitem>
142
        </varlistentry>
143

  
144
        <varlistentry>
145
          <term>plain</term>
146
	  <listitem><para>The instance will use LVM devices as backend for its
147
	  disks. No redundancy is provided.</para></listitem>
148
        </varlistentry>
149

  
150
        <varlistentry>
151
          <term>local_raid1</term>
152
	  <listitem><para>A local mirror is set between LVM devices to back the
153
	  instance. This provides some redundancy for the instance's
154
	  data.</para></listitem>
155
        </varlistentry>
156

  
157
        <varlistentry>
158
          <term>remote_raid1</term>
159
	  <listitem><para>A mirror is set between the local node and a remote
160
	  one, which must be specified with the --secondary-node option. Use
161
	  this option to obtain a highly available instance that can be failed
162
	  over to a remote node should the primary one fail.
163
	  </para></listitem>
164
        </varlistentry>
165

  
166
      </variablelist>
167

  
168
      For example if you want to create an highly available instance use the
169
      remote_raid1 disk template:
135 170
      <programlisting>
136 171
gnt-instance add -n TARGET_NODE -o OS_TYPE -t remote_raid1 \
137 172
  --secondary-node=SECONDARY_NODE INSTANCE_NAME
......
169 204
gnt-instance list
170 205
      </programlisting>
171 206
      </para>
207

  
208
      <para>Do not use the xen commands to stop instances. If you run for
209
      example xm shutdown or xm destroy on an instance Ganeti will
210
      automatically restart it (via the
211
      <citerefentry><refentrytitle>ganeti-watcher</refentrytitle>
212
      <manvolnum>8</manvolnum></citerefentry>)
213
      </para>
214

  
172 215
    </sect2>
173 216

  
174 217
    <sect2>
b/docs/installing.sgml
195 195
      </para>
196 196

  
197 197
      <para>
198
        If you want to add a device later you can do so with the vgextend(8)
199
        command.
198
	If you want to add a device later you can do so with the 
199
	<citerefentry><refentrytitle>vgextend</refentrytitle>
200
	<manvolnum>8</manvolnum></citerefentry> command.
200 201
        <programlisting>
201 202
pvcreate /dev/sdd
202 203
vgextend xenvg /dev/sdd

Also available in: Unified diff