Synnefo » snf-ganeti » ganeti-local

<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [

  <!-- Fill in your name for FIRSTNAME and SURNAME. -->

  <!-- Please adjust the date whenever revising the manpage. -->

  <!ENTITY dhdate      "<date>February 11, 2009</date>">

  <!-- SECTION should be 1-8, maybe w/ subsection other parameters are

       allowed: see man(7), man(1). -->

  <!ENTITY dhsection   "<manvolnum>8</manvolnum>">

  <!ENTITY dhucpackage "<refentrytitle>gnt-instance</refentrytitle>">

  <!ENTITY dhpackage   "gnt-instance">

  <!ENTITY debian      "<productname>Debian</productname>">

  <!ENTITY gnu         "<acronym>GNU</acronym>">

  <!ENTITY gpl         "&gnu; <acronym>GPL</acronym>">

  <!ENTITY footer SYSTEM "footer.sgml">

]>

<refentry>

  <refentryinfo>

    <copyright>

      <year>2006</year>

      <year>2007</year>

      <year>2008</year>

      <year>2009</year>

      <holder>Google Inc.</holder>

    </copyright>

    &dhdate;

  </refentryinfo>

  <refmeta>

    &dhucpackage;

    &dhsection;

    <refmiscinfo>ganeti 2.0</refmiscinfo>

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

    <refpurpose>ganeti instance administration</refpurpose>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

      <command>&dhpackage; </command>

      <arg choice="req">command</arg>

      <arg>arguments...</arg>

    </cmdsynopsis>

  </refsynopsisdiv>

  <refsect1>

    <title>DESCRIPTION</title>

    <para>

      The <command>&dhpackage;</command> is used for instance

      administration in the ganeti system.

    </para>

  </refsect1>

  <refsect1>

    <title>COMMANDS</title>

    <refsect2>

      <title>Creation/removal/querying</title>

      <refsect3>

        <title>ADD</title>

        <cmdsynopsis>

          <command>add</command>

          <sbr>

          <arg choice="req">-t<group choice="req">

              <arg>diskless</arg>

              <arg>file</arg>

              <arg>plain</arg>

              <arg>drbd</arg>

            </group></arg>

          <sbr>

          <group choice="req">

            <arg rep="repeat">--disk=<replaceable>N</replaceable>:size=<replaceable>VAL</replaceable><arg>,mode=<replaceable>ro|rw</replaceable></arg></arg>

            <arg>-s <replaceable>SIZE</replaceable></arg>

          </group>

          <sbr>

          <group>

            <arg rep="repeat">--net=<replaceable>N</replaceable><arg rep="repeat">:options</arg></arg>

            <arg>--no-nics</arg>

          </group>

          <sbr>

          <arg>-B <replaceable>BEPARAMS</replaceable></arg>

          <sbr>

          <arg>-H <replaceable>HYPERVISOR</replaceable><arg>:<arg choice="plain" rep="repeat">option=<replaceable>value</replaceable></arg></arg></arg>

          <sbr>

          <arg>--file-storage-dir <replaceable>dir_path</replaceable></arg>

          <arg>--file-driver<group choice="req">

              <arg>loop</arg>

              <arg>blktap</arg>

            </group></arg>

          <sbr>

          <group choice="req">

            <arg>-n <replaceable>node<optional>:secondary-node</optional></replaceable></arg>

            <arg>--iallocator <replaceable>name</replaceable></arg>

          </group>

          <sbr>

          <arg choice="req">-o <replaceable>os-type</replaceable></arg>

          <sbr>

          <arg>--submit</arg>

          <sbr>

          <arg choice="req"><replaceable>instance</replaceable></arg>

        </cmdsynopsis>

        <para>

          Creates a new instance on the specified host. The

          <replaceable>instance</replaceable> argument must be in DNS,

          but depending on the bridge setup, need not be in the same

          network as the nodes in the cluster.

        </para>

        <para>

          The <option>disk</option> option specifies the parameters

          for the disks of the instance. The numbering of disks starts

          at zero, and at least one disk needs to be passed. For each

          disk, at least the size needs to be given, and optionally

          the access mode (read-only or the default of read-write) can

          also be specified.  The size is interpreted (when no unit is

          given) in mebibytes. You can also use one of the suffixes

          <literal>m</literal>, <literal>g</literal> or

          <literal>t</literal> to specificy the exact the units used;

          these suffixes map to mebibytes, gibibytes and tebibytes.

        </para>

        <para>

          Alternatively, a single-disk instance can be created via the

          <option>-s</option> option which takes a single argument,

          the size of the disk. This is similar to the Ganeti 1.2

          version (but will only create one disk).

        </para>

        <para>

          The minimum disk specification is therefore

          <userinput>--disk 0:size=20G</userinput> (or <userinput>-s

          20G</userinput> when using the <option>-s</option> option),

          and a three-disk instance can be specified as

          <userinput>--disk 0:size=20G --disk 1:size=4G --disk

          2:size=100G</userinput>.

        </para>

        <para>

          The NICs of the instances can be specified via the

          <option>--nic</option> option. By default, one NIC is

          created for the instance, with a random MAC, and connected

          to the default bridge. Each NIC can take up to three

          parameters (all optional):

          <variablelist>

            <varlistentry>

              <term>mac</term>

              <listitem>

                <simpara>either a value or <constant>GENERATE</constant>

                  to generate a new unique MAC</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>ip</term>

              <listitem>

                <simpara>specifies the IP address assigned to the

                  instance from the Ganeti side (this is not necessarily

                  what the instance will use, but what the node expects

                  the instance to use)</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>bridge</term>

              <listitem>

                <simpara>specifies the bridge to attach this NIC

                  to</simpara>

              </listitem>

            </varlistentry>

          </variablelist>

        </para>

        <para>

          Alternatively, if no network is desired for the instance, you

          can prevent the default of one NIC with the

          <option>--no-nics</option> option.

        </para>

        <para>

          The <option>-o</option> options specifies the operating

          system to be installed. The available operating systems can

          be listed with <command>gnt-os list</command>.

        </para>

        <para>

          The <option>-B</option> option specifies the backend

          parameters for the instance. If no such parameters are

          specified, the values are inherited from the cluster. Possible

          parameters are:

          <variablelist>

            <varlistentry>

              <term>memory</term>

              <listitem>

                <simpara>the memory size of the instance; as usual,

                  suffixes can be used to denote the unit, otherwise the

                  value is taken in mebibites</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>vcpus</term>

              <listitem>

                <simpara>the number of VCPUs to assign to the instance

                  (if this value makes sense for the hypervisor)</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>auto_balance</term>

              <listitem>

                <simpara>whether the instance is considered in the N+1

                  cluster checks (enough redundancy in the cluster to

                  survive a node failure)</simpara>

              </listitem>

            </varlistentry>

          </variablelist>

        </para>

        <para>

          The <option>-H</option> option specified the hypervisor to

          use for the instance (must be one of the enabled hypervisors

          on the cluster) and optionally custom parameters for this

          instance. If not other options are used (i.e. the invocation

          is just <userinput>-H

          <replaceable>NAME</replaceable></userinput>) the instance

          will inherit the cluster options. The defaults below show

          the cluster defaults at cluster creation time.

        </para>

        <para>

          The possible hypervisor options are as follows:

          <variablelist>

            <varlistentry>

              <term>boot_order</term>

              <listitem>

                <simpara>Valid for the Xen HVM and KVM

                hypervisors.</simpara>

                <simpara>A string value denoting the boot order. This

                has different meaning for the Xen HVM hypervisor and

                for the KVM one.</simpara>

                <simpara>

                  For Xen HVM, The boot order is a string of letters

                  listing the boot devices, with valid device letters

                  being:

                </simpara>

                  <variablelist>

                    <varlistentry>

                      <term>a</term>

                      <listitem>

                        <para>

                          floppy drive

                        </para>

                      </listitem>

                    </varlistentry>

                    <varlistentry>

                      <term>c</term>

                      <listitem>

                        <para>

                          hard disk

                        </para>

                      </listitem>

                    </varlistentry>

                    <varlistentry>

                      <term>d</term>

                      <listitem>

                        <para>

                          CDROM drive

                        </para>

                      </listitem>

                    </varlistentry>

                    <varlistentry>

                      <term>n</term>

                      <listitem>

                        <para>

                          network boot (PXE)

                        </para>

                      </listitem>

                    </varlistentry>

                  </variablelist>

                <simpara>

                  The default is not to set an HVM boot order which is

                  interpreted as 'dc'.

                </simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>cdrom_image_path</term>

              <listitem>

                <simpara>Valid for the Xen HVM and KVM hypervisors.</simpara>

                <simpara>The path to a CDROM image to attach to the

                instance.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>nic_type</term>

              <listitem>

                <simpara>Valid for the Xen HVM and KVM hypervisors.</simpara>

                <para>

                  This parameter determines the way the network cards

                  are presented to the instance. The possible options are:

                  <simplelist>

                    <member>rtl8139 (default for Xen HVM) (HVM & KVM)</member>

                    <member>ne2k_isa (HVM & KVM)</member>

                    <member>ne2k_pci (HVM & KVM)</member>

                    <member>i82551 (KVM)</member>

                    <member>i82557b (KVM)</member>

                    <member>i82559er (KVM)</member>

                    <member>pcnet (KVM)</member>

                    <member>e1000 (KVM)</member>

                    <member>paravirtual (default for KVM) (HVM & KVM)</member>

                  </simplelist>

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>disk_type</term>

              <listitem>

                <simpara>Valid for the Xen HVM and KVM hypervisors.</simpara>

                <para>

                  This parameter determines the way the disks are

                  presented to the instance. The possible options are:

                  <simplelist>

                    <member>ioemu (default for HVM & KVM) (HVM & KVM)</member>

                    <member>ide (HVM & KVM)</member>

                    <member>scsi (KVM)</member>

                    <member>sd (KVM)</member>

                    <member>mtd (KVM)</member>

                    <member>pflash (KVM)</member>

                  </simplelist>

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>vnc_bind_address</term>

              <listitem>

                <simpara>Valid for the Xen HVM and KVM hypervisors.</simpara>

                <para>Specifies the address that the VNC listener for

                this instance should bind to. Valid values are IPv4

                addresses. Use the address 0.0.0.0 to bind to all

                available interfaces (this is the default) or specify

                the address of one of the interfaces on the node to

                restrict listening to that interface.</para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>vnc_tls</term>

              <listitem>

                <simpara>Valid for the KVM hypervisor.</simpara>

                <simpara>A boolean option that controls whether the

                VNC connection is secured with TLS.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>vnc_x509_path</term>

              <listitem>

                <simpara>Valid for the KVM hypervisor.</simpara>

                <para>If <option>vnc_tls</option> is enabled, this

                options specifies the path to the x509 certificate to

                use.</para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>vnc_x509_verify</term>

              <listitem>

                <simpara>Valid for the KVM hypervisor.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>acpi</term>

              <listitem>

                <simpara>Valid for the Xen HVM and KVM hypervisors.</simpara>

                <para>

                  A boolean option that specifies if the hypervisor

                  should enable ACPI support for this instance. By

                  default, ACPI is disabled.

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>pae</term>

              <listitem>

                <simpara>Valid for the Xen HVM and KVM hypervisors.</simpara>

                <para>

                  A boolean option that specifies if the hypervisor

                  should enabled PAE support for this instance. The

                  default is false, disabling PAE support.

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>kernel_path</term>

              <listitem>

                <simpara>Valid for the Xen PVM and KVM hypervisors.</simpara>

                <para>

                  This option specifies the path (on the node) to the

                  kernel to boot the instance with. Xen PVM instances

                  always require this, while for KVM if this option is

                  empty, it will cause the machine to load the kernel

                  from its disks.

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>initrd_path</term>

              <listitem>

                <simpara>Valid for the Xen PVM and KVM hypervisors.</simpara>

                <para>

                  This option specifies the path (on the node) to the

                  initrd to boot the instance with. Xen PVM instances

                  can use this always, while for KVM if this option is

                  only used if the <option>kernel_path</option> option

                  is also specified.

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>root_path</term>

              <listitem>

                <simpara>Valid for the Xen PVM and KVM hypervisors.</simpara>

                <para>

                  This options specifies the name of the root

                  device. This is always needed for Xen PVM, while for

                  KVM it is only used if the

                  <option>kernel_path</option> option is also

                  specified.

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>serial_console</term>

              <listitem>

                <simpara>Valid for the KVM hypervisor.</simpara>

                <simpara>This boolean option specifies whether to

                emulate a serial console for the instance.</simpara>

              </listitem>

            </varlistentry>

          </variablelist>

        </para>

        <para>

        </para>

        <para>

          The <option>--iallocator</option> option specifies the instance

          allocator plugin to use. If you pass in this option the allocator

          will select nodes for this instance automatically, so you don't need

          to pass them with the <option>-n</option> option. For more

          information please refer to the instance allocator documentation.

        </para>

        <para>

          The <option>-t</option> options specifies the disk layout type for

          the instance. The available choices are:

          <variablelist>

            <varlistentry>

              <term>diskless</term>

              <listitem>

                <para>

                  This creates an instance with no disks. Its useful for

                  testing only (or other special cases).

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>file</term>

              <listitem>

                <para>Disk devices will be regular files.</para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>plain</term>

              <listitem>

                <para>Disk devices will be logical volumes.</para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>drbd</term>

              <listitem>

                <para>

                  Disk devices will be drbd (version 8.x) on top of

                  lvm volumes.

                </para>

              </listitem>

            </varlistentry>

          </variablelist>

        </para>

        <para>

          The optional second value of the <option>--node</option> is used for

          the drbd template type and specifies the remote node.

        </para>

        <para>

          If you do not want gnt-instance to wait for the disk mirror

          to be synced, use the <option>--no-wait-for-sync</option>

          option.

        </para>

        <para>

          The <option>--file-storage-dir</option> specifies the relative path

          under the cluster-wide file storage directory to store file-based

          disks. It is useful for having different subdirectories for

          different instances. The full path of the directory where the disk

          files are stored will consist of cluster-wide file storage directory

          + optional subdirectory + instance name. Example:

          /srv/ganeti/file-storage/mysubdir/instance1.example.com. This option

          is only relevant for instances using the file storage backend.

        </para>

        <para>

          The <option>--file-driver</option> specifies the driver to use for

          file-based disks. Note that currently these drivers work with the

          xen hypervisor only. This option is only relevant for instances using

          the file storage backend. The available choices are:

          <variablelist>

            <varlistentry>

              <term>loop</term>

              <listitem>

                <para>

                  Kernel loopback driver. This driver uses loopback

                  devices to access the filesystem within the

                  file. However, running I/O intensive applications in

                  your instance using the loop driver might result in

                  slowdowns.  Furthermore, if you use the loopback

                  driver consider increasing the maximum amount of

                  loopback devices (on most systems it's 8) using the

                  max_loop param.

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>blktap</term>

              <listitem>

                <para>The blktap driver (for Xen hypervisors). In

                order to be able to use the blktap driver you should

                check if the 'blktapctrl' user space disk agent is

                running (usually automatically started via xend). This

                user-level disk I/O interface has the advantage of

                better performance. Especially if you use a network

                file system (e.g. NFS) to store your instances this is

                the recommended choice.

                </para>

              </listitem>

            </varlistentry>

          </variablelist>

        </para>

        <para>

          The <option>--submit</option> option is used to send the job to

          the master daemon but not wait for its completion. The job

          ID will be shown so that it can be examined via

          <command>gnt-job info</command>.

        </para>

        <para>

          Example:

          <screen>

# gnt-instance add -t file --disk 0:size=30g -B memory=512 -o debian-etch \

  -n node1.example.com --file-storage-dir=mysubdir instance1.example.com

# gnt-instance add -t plain --disk 0:size=30g -B memory=512 -o debian-etch \

  -n node1.example.com instance1.example.com

# gnt-instance add -t drbd --disk 0:size=30g -B memory=512 -o debian-etch \

  -n node1.example.com:node2.example.com instance2.example.com

          </screen>

        </para>

      </refsect3>

      <refsect3>

        <title>BATCH-CREATE</title>

        <cmdsynopsis>

          <command>batch-create</command>

          <arg choice="req">instances_file.json</arg>

        </cmdsynopsis>

        <para>

          This command (similar to the Ganeti 1.2

          <command>batcher</command> tool) submits multiple instance

          creation jobs based on a definition file. The instance

          configurations do not encompass all the possible options for

          the <command>add</command> command, but only a subset.

        </para>

        <para>

          The instance file should be a valid-formed JSON file,

          containing a dictionary with instance name and instance

          parameters. The accepted parameters are:

          <variablelist>

            <varlistentry>

              <term>disk_size</term>

              <listitem>

                <simpara>The size of the disks of the instance.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>disk_templace</term>

              <listitem>

                <simpara>The disk template to use for the instance,

                the same as in the <command>add</command>

                command.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>backend</term>

              <listitem>

                <simpara>A dictionary of backend parameters.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>hypervisor</term>

              <listitem>

                <simpara>A dictionary with a single key (the

                hypervisor name), and as value the hypervisor

                options. If not passed, the default hypervisor and

                hypervisor options will be inherited.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>mac, ip, bridge</term>

              <listitem>

                <simpara>Specifications for the one NIC that will be

                created for the instance.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>primary_node, secondary_node</term>

              <listitem>

                <simpara>The primary and optionally the secondary node

                to use for the instance (in case an iallocator script

                is not used).</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>iallocator</term>

              <listitem>

                <simpara>Instead of specifying the nodes, an

                iallocator script can be used to automatically compute

                them.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>start</term>

              <listitem>

                <simpara>whether to start the instance</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>ip_check</term>

              <listitem>

                <simpara>Skip the check for already-in-use instance;

                see the description in the <command>add</command>

                command for details.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>file_storage_dir, file_driver</term>

              <listitem>

                <simpara>Configuration for the <literal>file</literal>

                disk type, see the <command>add</command> command for

                details.</simpara>

              </listitem>

            </varlistentry>

          </variablelist>

        </para>

        <para>

          A simple definition for one instance can be (with most of

          the parameters taken from the cluster defaults):

          <screen>

{

  "instance3": {

    "template": "drbd",

    "os": "debootstrap",

    "disk_size": ["25G"],

    "iallocator": "dumb"

  },

  "instance5": {

    "template": "drbd",

    "os": "debootstrap",

    "disk_size": ["25G"],

    "iallocator": "dumb",

    "hypervisor": "xen-hvm",

    "hvparams": {"acpi": true},

    "backend": {"memory": 512}

  }

}

</screen>

        </para>

        <para>

          The command will display the job id for each submitted instance, as follows:

          <screen>

# gnt-instance batch-create instances.json

instance3: 11224

instance5: 11225

</screen>

        </para>

      </refsect3>

      <refsect3>

        <title>REMOVE</title>

        <cmdsynopsis>

          <command>remove</command>

          <arg>--ignore-failures</arg>

          <arg>--submit</arg>

          <arg choice="req"><replaceable>instance</replaceable></arg>

        </cmdsynopsis>

        <para>

          Remove an instance. This will remove all data from the

          instance and there is <emphasis>no way back</emphasis>. If

          you are not sure if you use an instance again, use

          <command>shutdown</command> first and leave it in the

          shutdown state for a while.

        </para>

        <para>

          The <option>--ignore-failures</option> option will cause the

          removal to proceed even in the presence of errors during the

          removal of the instance (e.g. during the shutdown or the

          disk removal). If this option is not given, the command will

          stop at the first error.

        </para>

        <para>

          The <option>--submit</option> option is used to send the job to

          the master daemon but not wait for its completion. The job

          ID will be shown so that it can be examined via

          <command>gnt-job info</command>.

        </para>

        <para>

          Example:

          <screen>

# gnt-instance remove instance1.example.com

          </screen>

        </para>

      </refsect3>

      <refsect3>

        <title>LIST</title>

        <cmdsynopsis>

          <command>list</command>

          <arg>--no-headers</arg>

          <arg>--separator=<replaceable>SEPARATOR</replaceable></arg>

          <arg>-o <replaceable>[+]FIELD,...</replaceable></arg>

          <arg rep="repeat">instance</arg>

        </cmdsynopsis>

        <para>

          Shows the currently configured instances with memory usage,

          disk usage, the node they are running on, and their run

          status.

        </para>

        <para>

          The <option>--no-headers</option> option will skip the

          initial header line. The <option>--separator</option> option

          takes an argument which denotes what will be used between

          the output fields. Both these options are to help scripting.

        </para>

        <para>

          The <option>-o</option> option takes a comma-separated list

          of output fields. The available fields and their meaning

          are:

          <variablelist>

            <varlistentry>

              <term>name</term>

              <listitem>

                <simpara>the instance name</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>os</term>

              <listitem>

                <simpara>the OS of the instance</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>pnode</term>

              <listitem>

                <simpara>the primary node of the instance</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>snodes</term>

              <listitem>

                <simpara>comma-separated list of secondary nodes for the

                  instance; usually this will be just one node</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>admin_state</term>

              <listitem>

                <simpara>the desired state of the instance (either "yes"

                  or "no" denoting the instance should run or

                  not)</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>disk_template</term>

              <listitem>

                <simpara>the disk template of the instance</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>oper_state</term>

              <listitem>

                <simpara>the actual state of the instance; can be

                one of the values "running", "stopped", "(node

                down)"</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>status</term>

              <listitem>

                <simpara>combined form of admin_state and oper_stat;

                this can be one of:

                <computeroutput>ERROR_nodedown</computeroutput> if the

                node of the instance is down,

                <computeroutput>ERROR_down</computeroutput> if the

                instance should run but is down,

                <computeroutput>ERROR_up</computeroutput> if the

                instance should be stopped but is actually running,

                <computeroutput>ADMIN_down</computeroutput> if the

                instance has been stopped (and is stopped) and

                <computeroutput>running</computeroutput> if the

                instance is set to be running (and is

                running)</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>oper_ram</term>

              <listitem>

                <simpara>the actual memory usage of the instance as seen

                  by the hypervisor</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>ip</term>

              <listitem>

                <simpara>the ip address ganeti recognizes as associated with

                the first instance interface</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>mac</term>

              <listitem>

                <simpara>the first instance interface MAC address</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>bridge</term>

              <listitem>

                <simpara>the bridge of the first instance NIC

                </simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>sda_size</term>

              <listitem>

                <simpara>the size of the instance's first disk</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>sdb_size</term>

              <listitem>

                <simpara>the size of the instance's second disk, if

                any</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>vcpus</term>

              <listitem>

                <simpara>the number of VCPUs allocated to the

                instance</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>tags</term>

              <listitem>

                <simpara>comma-separated list of the instances's

                tags</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>serial_no</term>

              <listitem>

                <simpara>the so called 'serial number' of the

                instance; this is a numeric field that is incremented

                each time the instance is modified, and it can be used

                to track modifications</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>network_port</term>

              <listitem>

                <simpara>If the instance has a network port assigned

                to it (e.g. for VNC connections), this will be shown,

                otherwise <literal>-</literal> will be

                displayed.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>beparams</term>

              <listitem>

                <simpara>A text format of the entire beparams for the

                instance. It's more useful to select individual fields

                from this dictionary, see below.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>disk.count</term>

              <listitem>

                <simpara>The number of instance disks.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>disk.size/N</term>

              <listitem>

                <simpara>The size of the instance's Nth disk. This is

                a more generic form of the <literal>sda_size</literal>

                and <literal>sdb_size</literal> fields.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>disk.sizes</term>

              <listitem>

                <simpara>A comma-separated list of the disk sizes for

                this instance.</simpara>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>disk_usage</term>