4 .. highlight:: shell-example
9 Most dependencies from :doc:`install-quick`, including ``qemu-img``
10 (marked there as optional) plus (for Python):
12 - `GNU make <http://www.gnu.org/software/make/>`_
13 - `GNU tar <http://www.gnu.org/software/tar/>`_
14 - `Gzip <http://www.gnu.org/software/gzip/>`_
15 - `pandoc <http://johnmacfarlane.net/pandoc/>`_
16 - `python-epydoc <http://epydoc.sourceforge.net/>`_
17 - `python-sphinx <http://sphinx.pocoo.org/>`_
18 (tested with version 1.1.3)
19 - `python-mock <http://www.voidspace.org.uk/python/mock/>`_
20 (tested with version 1.0.1)
21 - `graphviz <http://www.graphviz.org/>`_
22 - the `en_US.UTF-8` locale must be enabled on the system
23 - `pylint <http://www.logilab.org/857>`_ and its associated
25 - `pep8 <https://github.com/jcrocholl/pep8/>`_
26 - `PyYAML <http://pyyaml.org/>`_
28 For older developement (Ganeti < 2.4) ``docbook`` was used instead of
31 Note that for pylint, at the current moment the following versions
36 astng 0.23.1, common 0.58.0
38 The same with pep8, other versions may give you errors::
43 Both these versions are the ones shipped with Debian Wheezy.
45 To generate unittest coverage reports (``make coverage``), `coverage
46 <http://pypi.python.org/pypi/coverage>`_ needs to be installed.
48 Installation of all dependencies listed here::
50 $ apt-get install python-setuptools automake git fakeroot
51 $ apt-get install pandoc python-epydoc graphviz
52 $ apt-get install python-yaml
53 $ cd / && sudo easy_install \
55 logilab-astng==0.23.1 \
56 logilab-common==0.58.0 \
62 For Haskell development, again all things from the quick install
65 - `haddock <http://www.haskell.org/haddock/>`_, documentation
66 generator (equivalent to epydoc for Python)
67 - `HsColour <http://hackage.haskell.org/package/hscolour>`_, again
68 used for documentation (it's source-code pretty-printing)
69 - `hlint <http://community.haskell.org/~ndm/hlint/>`_, a source code
70 linter (equivalent to pylint for Python), recommended version 1.8 or
71 above (tested with 1.8.15)
72 - the `QuickCheck <http://hackage.haskell.org/package/QuickCheck>`_
74 - the `HUnit <http://hunit.sourceforge.net/>`_ library (tested with
77 <http://batterseapower.github.com/test-framework/>`_ libraries,
78 tested versions: ``test-framework``: 0.6, ``test-framework-hunit``:
79 0.2.7, ``test-framework-quickcheck2``: 0.2.12.1
80 - ``hpc``, which comes with the compiler, so you should already have
82 - `shelltestrunner <http://joyful.com/shelltestrunner>`_, used for
83 running shell-based unit-tests
84 - `temporary <https://github.com/batterseapower/temporary/>`_ library,
85 tested with version 1.1.2.3
87 Under Debian Wheezy or later, these can be installed (on top of the
88 required ones from the quick install document) via::
90 $ apt-get install libghc-quickcheck2-dev libghc-hunit-dev \
91 libghc-test-framework-dev \
92 libghc-test-framework-quickcheck2-dev \
93 libghc-test-framework-hunit-dev \
94 libghc-temporary-dev \
97 Or alternatively via ``cabal``::
99 $ cabal install QuickCheck HUnit \
100 test-framework test-framework-quickcheck2 test-framework-hunit \
101 temporary hscolour hlint shelltestrunner
104 Configuring for development
105 ---------------------------
107 Run the following command (only use ``PYTHON=...`` if you need to use a
108 different python version)::
111 ./configure --prefix=/usr/local --sysconfdir=/etc --localstatedir=/var
113 Note that doing development on a machine which already has Ganeti
114 installed is problematic, as ``PYTHONPATH`` behaviour can be confusing
115 (see Issue 170 for a bit of history/details; in general it works if
116 the installed and developed versions are very similar, and/or if
117 PYTHONPATH is customised correctly). As such, in general it's
118 recommended to use a "clean" machine for ganeti development.
120 Haskell development notes
121 -------------------------
123 There are a few things which can help writing or debugging the Haskell
126 You can run the Haskell linter :command:`hlint` via::
130 This is not enabled by default (as the htools component is
131 optional). The above command will generate both output on the terminal
132 and, if any warnings are found, also an HTML report at
133 ``doc/hs-lint.html``.
135 When writing or debugging TemplateHaskell code, it's useful to see
136 what the splices are converted to. This can be done via::
138 $ make HEXTRA="-ddump-splices"
140 Or, more interactively::
143 λ> :set -ddump-splices
144 λ> :l src/Ganeti/Objects.hs
146 And you will get the spliced code as the module is loaded.
148 To build profiling code you must install the ``ghc-prof`` (or
149 ``gch6-prof``) package, and all the relevant libraries with their
150 ``-prof`` counterparts. If installing libraries through cabal the config
151 file should include ``library-profiling: True`` or the ``-p`` flag
152 should be used. Any library already installed can be updated by passing
153 ``--reinstall`` as well.
155 Due to the way TemplateHaskell works, it's not straightforward to
156 build profiling code. The recommended way is to run ``make hs-prof``,
157 or alternatively the manual sequence is::
160 $ make src/htools HEXTRA="-osuf .o"
162 $ make src/htools HEXTRA="-osuf .prof_o -prof -auto-all"
164 This will build the binary twice, per the TemplateHaskell
165 documentation, the second one with profiling enabled.
167 The binary files generated by compilation and the profiling/coverage
168 files can "break" tab-completion in the sources; they can be ignored,
169 for example, in bash via ``.bashrc``::
171 FIGNORE='.o:.hi:.prof_o:.tix'
173 or in emacs via ``completion-ignored-extensions`` (run ``M-x
174 customize-var completion-ignored-extensions``).
176 Running individual tests
177 ~~~~~~~~~~~~~~~~~~~~~~~~
179 When developing code, running the entire test suite can be
180 slow. Running individual tests is possible. There are different
181 Makefile targets for running individual Python and Haskell tests.
185 $ export PYTHONPATH=$PWD
186 $ python ./test/py/ganeti.%mytest%
190 $ make hs-test-%pattern%
192 Where ``pattern`` can be a simple test pattern (e.g. ``comma``,
193 matching any test whose name contains ``comma``), a test pattern
194 denoting a group (ending with a slash, e.g. ``Utils/``), or more
195 complex glob pattern. For more details, search for glob patterns in
196 the documentation of `test-framework
197 <http://batterseapower.github.com/test-framework/>`_).
199 For individual Haskell shelltests::
201 $ make hs-shell-%name%
203 which runs the test ``test/hs/shelltests/htools-%name%.test``. For
204 example, to run the test ``test/hs/shelltests/htools-balancing.test``,
207 $ make hs-shell-balancing
209 For combined Haskell shelltests::
211 $ make hs-shell-{%name1%,%name2%,...}
215 $ make hs-shell-{balancing,basic}
220 Ganeti is mostly developed and tested on `Debian
221 <http://www.debian.org/>`_-based distributions, while still keeping
222 adaptability to other Linux distributions in mind.
224 The ``doc/examples/`` directory contains a number of potentially useful
225 scripts and configuration files. Some of them might need adjustment
231 This script, in the source code as ``daemons/daemon-util.in``, is used
232 to start/stop Ganeti and do a few other things related to system
233 daemons. It is recommended to use ``daemon-util`` also from the system's
234 init scripts. That way the code starting and stopping daemons is shared
235 and future changes have to be made in only one place.
237 ``daemon-util`` reads extra arguments from variables (``*_ARGS``) in
238 ``/etc/default/ganeti``. When modifying ``daemon-util``, keep in mind to
239 not remove support for the ``EXTRA_*_ARGS`` variables for starting
240 daemons. Some parts of Ganeti use them to pass additional arguments when
243 The ``reload_ssh_keys`` function can be adjusted to use another command
244 for reloading the OpenSSH daemon's host keys.
246 .. vim: set textwidth=72 :