Revision 33ea43b6

b/doc/admin.rst
320 320
Importing an instance is similar to creating a new one, but additionally
321 321
one must specify the location of the snapshot. The command is::
322 322

  
323
  gnt-backup import -n TARGET_NODE -t DISK_TEMPLATE \
323
  gnt-backup import -n TARGET_NODE \
324 324
    --src-node=NODE --src-dir=DIR INSTANCE_NAME
325 325

  
326
Most of the options available for the command :command:`gnt-instance
327
add` are supported here too.
326
By default, parameters will be read from the export information, but you
327
can of course pass them in via the command line - most of the options
328
available for the command :command:`gnt-instance add` are supported here
329
too.
328 330

  
329 331
Import of foreign instances
330 332
+++++++++++++++++++++++++++
b/man/gnt-backup.sgml
21 21
      <year>2007</year>
22 22
      <year>2008</year>
23 23
      <year>2009</year>
24
      <year>2010</year>
24 25
      <holder>Google Inc.</holder>
25 26
    </copyright>
26 27
    &dhdate;
......
29 30
    &dhucpackage;
30 31

  
31 32
    &dhsection;
32
    <refmiscinfo>ganeti 2.0</refmiscinfo>
33
    <refmiscinfo>ganeti 2.1</refmiscinfo>
33 34
  </refmeta>
34 35
  <refnamediv>
35 36
    <refname>&dhpackage;</refname>
......
135 136
        <arg>--src-dir=<replaceable>source-dir</replaceable></arg>
136 137
        <sbr>
137 138

  
138
        <arg choice="req">-t<group>
139
        <arg choice="opt">-t<group>
139 140
            <arg>diskless</arg>
140 141
            <arg>plain</arg>
141 142
            <arg>drbd</arg>
......
143 144
          </group></arg>
144 145
        <sbr>
145 146

  
147
        <arg choice="opt">--identify-defaults</arg>
148
        <sbr>
149

  
146 150
        <arg choice="req"><replaceable>instance</replaceable></arg>
147 151
      </cmdsynopsis>
152

  
148 153
      <para>
149 154
        Imports a new instance from an export residing on
150 155
        <replaceable>source-node</replaceable> in
......
159 164
      <para>
160 165
        The <option>disk</option> option specifies the parameters for
161 166
        the disks of the instance. The numbering of disks starts at
162
        zero, and at least one disk needs to be passed. For each disk,
163
        at least the size needs to be given, and optionally the access
164
        mode (read-only or the default of read-write) can also be
165
        specified.  The size is interpreted (when no unit is given) in
166
        mebibytes. You can also use one of the suffixes
167
        zero. For each disk, at least the size needs to be given, and
168
        optionally the access mode (read-only or the default of
169
        read-write) can also be specified.  The size is interpreted
170
        (when no unit is given) in mebibytes. You can also use one of
171
        the suffixes
167 172
        <literal>m</literal>, <literal>g</literal> or
168 173
        <literal>t</literal> to specificy the exact the units used;
169 174
        these suffixes map to mebibytes, gibibytes and tebibytes.
......
177 182
      </para>
178 183

  
179 184
      <para>
180
        The minimum disk specification is therefore
185
        If no disk information is passed, the disk configuration saved
186
        at export time will be used.
187
      </para>
188

  
189
      <para>
190
        The minimum disk specification is therefore empty (export
191
        information will be used), a single disk can be specified as
181 192
        <userinput>--disk 0:size=20G</userinput> (or <userinput>-s
182 193
          20G</userinput> when using the <option>-s</option> option),
183 194
        and a three-disk instance can be specified as
......
187 198

  
188 199
      <para>
189 200
        The NICs of the instances can be specified via the
190
        <option>--net</option> option. By default, one NIC is created
191
        for the instance, with the MAC set to the original MAC of the
192
        instance (as it was at export time). Each NIC can take up to
193
        three parameters (all optional):
201
        <option>--net</option> option. By default, the NIC
202
        configuration of the original (exported) instance will be
203
        reused. Each NIC can take up to three parameters (all
204
        optional):
194 205
        <variablelist>
195 206
          <varlistentry>
196 207
            <term>mac</term>
......
232 243
      </para>
233 244

  
234 245
      <para>
235
        Alternatively, if no network is desired for the instance, you
236
        can prevent the default of one NIC with the
237
        <option>--no-nics</option> option.
246
        If no network is desired for the instance, you should create a
247
        single empty NIC and delete it afterwards
248
        via <command>gnt-instance modify --net delete</command>.
238 249
      </para>
239 250

  
240 251
      <para>
241 252
        The <option>-B</option> option specifies the backend
242 253
        parameters for the instance. If no such parameters are
243
        specified, the values are inherited from the cluster. Possible
254
        specified, the values are inherited from the export. Possible
244 255
        parameters are:
245 256
        <variablelist>
246 257
          <varlistentry>
......
270 281
      </para>
271 282

  
272 283
      <para>
273
        The <option>-t</option> options specifies the disk layout type for
274
        the instance. The available choices are:
284
        The <option>-t</option> options specifies the disk layout type
285
        for the instance. If not passed, the configuration of the
286
        original instance is used. The available choices are:
275 287
        <variablelist>
276 288
          <varlistentry>
277 289
            <term>diskless</term>
......
326 338
      </para>
327 339

  
328 340
      <para>
329
        If you do not want gnt-backup to wait for the disk mirror
330
        to be synced, use the <option>--no-wait-for-sync</option>
331
        option.
341
        Since many of the parameters are by default read from the
342
        exported instance information and used as such, the new
343
        instance will have all parameters explicitly specified, the
344
        opposite of a newly added instance which has most parameters
345
        specified via cluster defaults. To change the import behaviour
346
        to recognize parameters whose saved value matches the current
347
        cluster default and mark it as such (default value), pass
348
        the <option>--identify-defaults</option> option. This will
349
        affect the hypervisor, backend and NIC parameters, both read
350
        from the export file and passed in via the command line.
332 351
      </para>
333 352

  
334 353
      <para>
335
        Example:
354
        Example for identical instance import:
355
        <screen>
356
# gnt-backup import -n node1.example.com instance3.example.com
357
        </screen>
358
      </para>
359
      <para>
360
        Explicit configuration example:
336 361
        <screen>
337 362
# gnt-backup import -t plain --disk 0:size=1G -B memory=512 \
338 363
> -n node1.example.com \

Also available in: Unified diff