The constants in this module are used in Haskell and are also
converted to Python.

Do not write any definitions in this file other than constants. Do
not even write helper functions. The definitions in this module are
automatically stripped to build the Makefile.am target
hs. If there are helper functions in this module,
they will also be dragged and it will cause compilation to fail.
Therefore, all helper functions should go to a separate module and
imported.

A Xen-specific implementation detail is that there is no way to
actually say use any cpu for pinning in a Xen configuration file,
as opposed to the command line, where you can say
xm vcpu-pin domainvcpu all

For the format, see ciphers(1). A better way to disable ciphers
would be to use the exclamation mark (!), but socat versions below
1.5 can't parse exclamation marks in options properly. When
modifying the ciphers, ensure not to accidentially add something
after it's been removed. Use the openssl utility to check the
allowed ciphers, e.g. openssl ciphers -v HIGH:-DES.

This is used to order determine the default disk template when
the list of enabled disk templates is inferred from the current
state of the cluster. This only happens on an upgrade from a
version of Ganeti that did not support the enabled_disk_templates
so far.

The default values for the DRBD dynamic resync speed algorithm are
taken from the drbsetup 8.3.11 man page, except for c-plan-ahead
(that we don't need to set to 0, because we have a separate option
to enable it) and for c-max-rate, that we cap to the default value
for the static resync rate.

Exclusive storage

Luxid job scheduling

Time intervall in seconds for polling updates on the job queue. This
intervall is only relevant if the number of running jobs reaches the maximal
allowed number, as otherwise new jobs will be started immediately anyway.
Also, as jobs are watched via inotify, scheduling usually works independent
of polling. Therefore we chose a sufficiently large interval, in the order of
5 minutes. As with the interval for reloading the configuration, we chose a
prime number to avoid accidental 'same wakeup' with other processes.

The default value for the maximal number of jobs to be running at the same
time. Once the maximal number is reached, new jobs will just be queued and
only started, once some of the other jobs have finished.

When we haven't reloaded the config for more than this amount of
seconds, we force a test to see if inotify is betraying us. Using a
prime number to ensure we get less chance of 'same wakeup' with
other processes.

By default a confd request is sent to the minimum between this
number and all MCs. 6 was chosen because even in the case of a
disastrous 50% response rate, we should have enough answers to be
able to compare more than one.