Please note that a more detailed installation procedure is described in the Ganeti installation tutorial. Refer to it if you are setting up Ganeti the first time. This quick installation guide is mainly meant as reference for experienced users. A glossary of terms can be found in the Glossary.
Before installing, please verify that you have the following programs:
These programs are supplied as part of most Linux distributions, so usually they can be installed via the standard package manager. Also many of them will already be installed on a standard machine. On Debian/Ubuntu, you can use this command line to install all required packages, except for RBD, DRBD and Xen:
$ apt-get install lvm2 ssh bridge-utils iproute iputils-arping make m4 \
ndisc6 python python-openssl openssl \
python-pyparsing python-simplejson python-bitarray \
python-pyinotify python-pycurl python-ipaddr socat fping
For older distributions (eg. Debian Squeeze) the package names are different.:
$ apt-get install lvm2 ssh bridge-utils iproute iputils-arping make \
ndisc6 python python-pyopenssl openssl \
python-pyparsing python-simplejson python-bitarray \
python-pyinotify python-pycurl python-ipaddr socat fping
If bitarray is missing it can be installed from easy-install:
$ easy_install bitarray
Note that this does not install optional packages:
$ apt-get install python-paramiko python-affinity qemu-utils
If some of the python packages are not available in your system, you can try installing them using easy_install command. For example:
$ apt-get install python-setuptools python-dev
$ cd / && easy_install \
affinity \
bitarray \
ipaddr
On Fedora to install all required packages except RBD, DRBD and Xen:
$ yum install openssh openssh-clients bridge-utils iproute ndisc6 make \
pyOpenSSL pyparsing python-simplejson python-inotify \
python-lxm socat fping python-bitarray python-ipaddr
For optional packages use the command:
$ yum install python-paramiko python-affinity qemu-img
If you want to build from source, please see doc/devnotes.rst for more dependencies.
Note
Ganeti’s import/export functionality uses socat with OpenSSL for transferring data between nodes. By default, OpenSSL 0.9.8 and above employ transparent compression of all data using zlib if supported by both sides of a connection. In cases where a lot of data is transferred, this can lead to an increased CPU usage. Additionally, Ganeti already compresses all data using gzip where it makes sense (for inter-cluster instance moves).
To remedey this situation, patches implementing a new socat option for disabling OpenSSL compression have been contributed and will likely be included in the next feature release. Until then, users or distributions need to apply the patches on their own.
Ganeti will use the option if it’s detected by the configure script; auto-detection can be disabled by explicitly passing --enable-socat-compress (use the option to disable compression) or --disable-socat-compress (don’t use the option).
The patches and more information can be found on http://www.dest-unreach.org/socat/contrib/socat-opensslcompress.html.
Starting with Ganeti 2.7, the Haskell GHC compiler and a few base libraries are required in order to build Ganeti (but not to run and deploy Ganeti on production machines). More specifically:
Some of these are also available as package in Debian/Ubuntu:
$ apt-get install ghc libghc-json-dev libghc-network-dev \
libghc-parallel-dev libghc-deepseq-dev \
libghc-utf8-string-dev libghc-curl-dev \
libghc-hslogger-dev
Or in older versions of these distributions (using GHC 6.x):
$ apt-get install ghc6 libghc6-json-dev libghc6-network-dev \
libghc6-parallel-dev libghc6-deepseq-dev \
libghc6-curl-dev
In Fedora, some of them are available via packages as well:
$ yum install ghc ghc-json-devel ghc-network-devel \
ghc-parallel-devel ghc-deepseq-devel
If using a distribution which does not provide them, first install the Haskell platform. You can also install cabal manually:
$ apt-get install cabal-install
$ cabal update
Then install the additional libraries (only the ones not available in your distribution packages) via cabal:
$ cabal install json network parallel utf8-string curl hslogger
Optionally, more functionality can be enabled if your build machine has a few more Haskell libraries enabled: the ganeti-confd and ganeti-luxid daemon (--enable-confd) and the monitoring daemon (--enable-mond). The list of extra dependencies for these is:
These libraries are available in Debian Wheezy (but not in Squeeze), so you can use either apt:
$ apt-get install libghc-crypto-dev libghc-text-dev \
libghc-hinotify-dev libghc-regex-pcre-dev \
libpcre3-dev \
libghc-attoparsec-dev libghc-vector-dev \
libghc-snap-server-dev
or cabal, after installing a required non-Haskell dependency:
$ apt-get install libpcre3-dev libcurl4-openssl-dev
$ cabal install Crypto text hinotify==0.3.2 regex-pcre \
attoparsec vector snap-server
to install them.
In case you still use ghc-6.12, note that cabal would automatically try to install newer versions of some of the libraries snap-server depends on, that cannot be compiled with ghc-6.12, so you have to install snap-server on its own, explicitly forcing the installation of compatible versions:
$ cabal install MonadCatchIO-transformers==0.2.2.0 mtl==2.0.1.0 \
hashable==1.1.2.0 case-insensitive==0.3 parsec==3.0.1 \
network==2.3 snap-server==0.8.1
The most recent Fedora doesn’t provide crypto, inotify. So these need to be installed using cabal, if desired. The other packages can be installed via yum:
$ yum install ghc-hslogger-devel ghc-text-devel \
ghc-regex-pcre-devel
Note
If one of the cabal packages fails to install due to unfulfilled dependencies, you can try enabling symlinks in ~/.cabal/config.
Make sure that your ~/.cabal/bin directory (or whatever else is defined as bindir) is in your PATH.
To install, simply run the following command:
$ ./configure --localstatedir=/var --sysconfdir=/etc && \
make && \
make install
This will install the software under /usr/local. You then need to copy doc/examples/ganeti.initd to /etc/init.d/ganeti and integrate it into your boot sequence (chkconfig, update-rc.d, etc.).
Before initialising the cluster, on each node you need to create the following directories:
After this, use gnt-cluster init.