Synnefo » snf-ganeti » ganeti-local

- `DRBD <http://www.drbd.org/>`_, kernel module and userspace utils,

  version 8.0.7 or above

- `LVM2 <http://sourceware.org/lvm2/>`_

- `OpenSSH <http://www.openssh.com/portable.html>`_

- `bridge utilities <http://www.linuxfoundation.org/en/Net:Bridge>`_

- `iproute2 <http://www.linuxfoundation.org/en/Net:Iproute2>`_

Version 2.2.0

-------------

- RAPI now requires a Content-Type header for requests with a body (e.g.

  ``PUT`` or ``POST``) which must be set to ``application/json`` (see

  RFC2616 (HTTP/1.1), section 7.2.1)

Version 2.1.3

==========

For installation instructions, read the INSTALL and the doc/install.html

  Mon Oct 26 00:22:52 2009 adding instance instance1 to cluster config

  Mon Oct 26 00:22:52 2009  - INFO: Waiting for instance instance1 to sync disks.

  …

  Mon Oct 26 00:23:03 2009 * running the instance OS create scripts...

  Mon Oct 26 00:23:13 2009 * starting instance...

  node1#

recreated from it and if the instance disks have not been lost it

permits recovery from the loss of all master candidates.

Other Ganeti projects

---------------------

# General information about the project.

project = u'Ganeti'

# The version info for the project you're documenting, acts as replacement for

# |version| and |release|, also used in various other places throughout the

    <para>

      Report bugs to <ulink

      url="http://code.google.com/p/ganeti/"></ulink> or contact the

      <ganeti@googlegroups.com>.

    </para>

  </refsect1>

    <title>COPYRIGHT</title>

    <para>

      granted to copy, distribute and/or modify under the terms of the

      &gnu; General Public License as published by the Free Software

      Foundation; either version 2 of the License, or (at your option)

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

        The confd protocol is an HMAC authenticated json-encoded custom format,

        over UDP. A client library is provided to make it easy to write

        software to query confd. More information can be found in the Ganeti

      </para>

    </refsect2>

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

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

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

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

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

    <copyright>

      <year>2008</year>

      <year>2009</year>

      <holder>Google Inc.</holder>

    </copyright>

    &dhdate;

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

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

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

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

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

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

      <year>2007</year>

      <year>2008</year>

      <year>2009</year>

      <holder>Google Inc.</holder>

    </copyright>

    &dhdate;

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

    <para>

      The <command>&dhpackage;</command> is the daemon which is

    </para>

    <para>

      By default, in order to be able to support features such as node

    </para>

    <para>

    </para>

    <para>

    </para>

    <para>

      Ganeti noded communication is protected via SSL, with a key generated at

      cluster init time. This can be disabled with the

      can be specified using the <option>-K</option> and <option>-C</option>

      options.

    </para>

    <refsect2>

      <title>COMMUNICATION PROTOCOL</title>

      <para>

      </para>

    </refsect2>

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>ganeti-os-interface</refname>

  </refnamediv>

  <refsect1>

        <varlistentry>

          <term>OS_API_VERSION</term>

          <listitem>

            environment conforms to.</simpara>

          </listitem>

        </varlistentry>

        <varlistentry>

          <term>INSTANCE_OS</term>

          <listitem>

            it. This can simplify the OS scripts by providing the same

            scripts under multiple names, and then the scripts can use

            this name to alter their behaviour.</simpara>

            on this variable is deprecated: OS_VARIANT should be used

            instead (see below).</simpara>

          </listitem>

            must support all variants listed under its

            <filename>variants.list</filename> file, and may support more.

            Any more supported variants should be properly documented in the

          </listitem>

        </varlistentry>

        <varlistentry>

      <para>The <envar>INSTANCE_REINSTALL</envar> variable is set to '1' when

      this create request is reinstalling and existing instance, rather than

      creating one anew. This can be used, for example, to preserve some

    </refsect2>

      <title>ganeti_api_version</title>

      <para>

        The <filename>ganeti_api_version</filename> file is a plain

        this OS definition complies with, one per line. The version

        documented by this man page is 15, so this file must contain

        the number 15 followed by a newline if only this version is

        should contain the most recent version first (i.e. 15),

        followed by the old version(s) (in this case 10 and/or 5).

      </para>

    <title>NOTES</title>

    <refsect2>

      <para>

        file is ignored and no OS_VARIANT environment variable is

        passed.

      </para>

        <title>Version 5 to 10</title>

        <para>

          options to environment variables, so scripts should be

          modified to use these. For an example of how this can be

          done in a way compatible with both versions, feel free to

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

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

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

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

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

    <copyright>

      <year>2008</year>

      <year>2009</year>

      <holder>Google Inc.</holder>

    </copyright>

    &dhdate;

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

    read-write rights, whereas the second user does only have read

    (query) rights, and as such is no different than not using

    authentication at all.</para>

  </refsect1>

  &footer;

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

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

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

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

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

      <year>2007</year>

      <year>2008</year>

      <year>2009</year>

      <holder>Google Inc.</holder>

    </copyright>

    &dhdate;

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

      <para>

        In addition, it will execute any scripts which exist under the

        (@SYSCONFDIR@/ganeti/hooks). This should be used for

        lightweight actions, like starting any extra daemons.

      </para>

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

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

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

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

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

      <year>2007</year>

      <year>2008</year>

      <year>2009</year>

      <holder>Google Inc.</holder>

    </copyright>

    &dhdate;

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

    <title>DESCRIPTION</title>

    <para>

      of a cluster based on a virtualization software. The current

    </para>

  </refsect1>

          <varlistentry>

            <term>offline</term>

            <listitem>

              configuration, but except for the master daemon startup

              voting procedure, they are not actually contacted by the

              master. This state was added in order to allow broken

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

    <para>

      The <command>&dhpackage;</command> is used for importing and exporting

    </para>

  </refsect1>

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

    <para>

      The <command>&dhpackage;</command> is used for cluster-wide

    </para>

  </refsect1>

      <para>

        The <option>-g</option> option will let you specify a volume group

        This volume group must have the same name on all nodes. Once the

        cluster is initialized this can be altered by using the

        <command>modify</command> command. If you don't want to use lvm

      <para>

        The <option>--no-voting</option> option skips the remote node agreement

        checks. This is dangerous, but necessary in some cases (for example

      </para>

    </refsect2>

      </para>

      <para>

        check whether if it loses a node it can restart all the instances on

        their secondaries (and report an error otherwise).

      </para>

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

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

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

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

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

      <year>2007</year>

      <year>2008</year>

      <year>2009</year>

      <holder>Google Inc.</holder>

    </copyright>

    &dhdate;

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

    <para>

      The <command>&dhpackage;</command> is used for debugging the

    </para>

  </refsect1>

      </para>

      <para>

        following directories: <filename

        class="directory">@CUSTOM_IALLOCATOR_SEARCH_PATH@</filename>;

        for more details about this framework, see the HTML or PDF

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

    <para>

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

    </para>

  </refsect1>

                <quote>none</quote>, <quote>user</quote> or

                <quote>pool</quote>. Under <quote>none</quote>, the

                default, nothing is done and instances are run as

                </simpara>

                <simpara>Under <quote>user</quote> kvm will drop

              <listitem>

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

                existing on the host.

                </simpara>

                <simpara>Cannot be set under security model <quote>none</quote>

                instance in a chroot directory.

                </simpara>

                <para>If it is set to <quote>true</quote>, an empty directory

                The directory is removed when the instance is stopped.

                </para>

            <varlistentry>

              <term>ip</term>

              <listitem>

                the first instance interface</simpara>

              </listitem>

            </varlistentry>

        <para>

          If the <option>--cleanup</option> option is passed, the

          operation changes from migration to attempting recovery from

          the instance runs on the correct node (and updates its

          configuration if not) and ensures the instances's disks are

          configured correctly. In this mode, the

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

    <para>

      The <command>&dhpackage;</command> is used for managing the

    </para>

  </refsect1>

        This command is used to join a new node to the cluster. You

        will have to provide the password for root of the node to be

        able to add the node in the cluster. The command needs to be

      </para>

      <para>

        This commands (tries to) forcefully reboot a node. It is a

        command that can be used if the node environemnt is broken,

        such that the admin can no longer login over ssh, but the

      </para>

      <para>

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

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

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

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

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

    &dhucpackage;

    &dhsection;

  </refmeta>

  <refnamediv>

    <refname>&dhpackage;</refname>

  </refnamediv>

  <refsynopsisdiv>

    <cmdsynopsis>

    <para>

      The <command>&dhpackage;</command> is used for managing the list

      of available operating system flavours for the instances in the

    </para>

  </refsect1>