Synnefo » snf-ganeti

Before installing, please verify that you have the following programs:

  - Xen virtualization (version 3.0.x or 3.1)

    http://xen.xensource.com/

    http://www.drbd.org/

  - LVM2

    http://sourceware.org/lvm2/

    http://developer.osdl.org/dev/iproute2

  - arping (part of iputils package)

    ftp://ftp.inr.ac.ru/ip-routing/iputils-current.tar.gz

  - Python 2.4

    http://www.python.org

  - Python Twisted library (the core is enough)

security model is all-or-nothing.

All the Ganeti code runs as root, because all the operations that Ganeti

starting instances, etc. Running as root does not mean setuid, but that

you need to be root to run the cluster commands.

Note that only the ssh key will allow other machines to run random

commands on this node; the RPC method will run only:

  - well defined commands to create, remove, activate logical volumes,

  - run ssh commands on other nodes in the cluster, again well-defined

  - scripts under the /etc/ganeti/hooks directory

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

            <arg>diskless</arg>

            <arg>plain</arg>

            <arg>drbd</arg>

          </group></arg>

        <sbr>

            </listitem>

          </varlistentry>

          <varlistentry>

            <term>drbd</term>

            <listitem>

              <para>

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

              </para>

            </listitem>

          </varlistentry>

      </para>

      <para>

      </para>

      <para>

        <para>

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

        </para>

        <para>

          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>

          Example:

          Show detailed information about the (given) instances. This

          is different from <command>list</command> as it shows

          detailed data about the instance's disks (especially useful

        </para>

      </refsect3>

        <cmdsynopsis>

          <command>replace-disks</command>

          <arg choice="opt">-s</arg>

          <arg choice="req">--new-secondary <replaceable>NODE</replaceable></arg>

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

        <para>

          This command is a generalized form for adding and replacing

        </para>

        <para>

          (<option>-p</option>) or the secondary (<option>-s</option>)

          node of the instance only, without changing the node.

        </para>

          successful, the command will show the location and name of

          the block devices:

          <screen>

          </screen>

          In this example, <emphasis>node1.example.com</emphasis> is

          the name of the node on which the devices have been

          activated. The <emphasis>sda</emphasis> and

          <emphasis>sdb</emphasis> are the names of the block devices

          devices as visible on the node.

        </para>

        </cmdsynopsis>

        <para>

          De-activates the block devices of the given instance. Note

        </para>

      </refsect3>

        <para>

          Failover will fail the instance over its secondary

        </para>

        <para>

        This command will change the secondary node from the source

        node to the destination node for all instances having the

        source node as secondary. It works only for instances having

      </para>

      <para>

      <para>

        This command will fail over all instances having the given

        node as primary to their secondary nodes. This works only for

      </para>

      <para>