Revision a6243496
b/man/ganeti-confd.rst | ||
---|---|---|
1 |
ganeti-confd(8) Ganeti | Version @GANETI_VERSION@ |
|
2 |
================================================= |
|
3 |
|
|
4 |
Name |
|
5 |
---- |
|
6 |
|
|
7 |
ganeti-confd - Ganeti conf daemon |
|
8 |
|
|
9 |
Synopsis |
|
10 |
-------- |
|
11 |
|
|
12 |
**ganeti-confd** [-f] [-d] |
|
13 |
|
|
14 |
DESCRIPTION |
|
15 |
----------- |
|
16 |
|
|
17 |
**ganeti-confd** is a daemon used to answer queries related to the |
|
18 |
configuration of a Ganeti cluster. |
|
19 |
|
|
20 |
For testing purposes, you can give the ``-f`` option and the |
|
21 |
program won't detach from the running terminal. |
|
22 |
|
|
23 |
Debug-level message can be activated by giving the ``-d`` option. |
|
24 |
|
|
25 |
ROLE |
|
26 |
~~~~ |
|
27 |
|
|
28 |
The role of the conf daemon is to make sure we have a highly available |
|
29 |
and very fast way to query cluster configuration values. This daemon |
|
30 |
is automatically active on all master candidates, and so has no single |
|
31 |
point of failure. It communicates via UDP so each query can easily be |
|
32 |
sent to multiple servers, and it answers queries from a cached copy of |
|
33 |
the config it keeps in memory, so no disk access is required to get an |
|
34 |
answer. |
|
35 |
|
|
36 |
The config is reloaded from disk automatically when it changes, with a |
|
37 |
rate limit of once per second. |
|
38 |
|
|
39 |
If the conf daemon is stopped on all nodes, its clients won't be able |
|
40 |
to get query answers. |
|
41 |
|
|
42 |
COMMUNICATION PROTOCOL |
|
43 |
~~~~~~~~~~~~~~~~~~~~~~ |
|
44 |
|
|
45 |
The confd protocol is an HMAC authenticated json-encoded custom |
|
46 |
format, over UDP. A client library is provided to make it easy to |
|
47 |
write software to query confd. More information can be found in the |
|
48 |
Ganeti 2.1 design doc, and an example usage can be seen in the |
|
49 |
(external) NBMA daemon for Ganeti. |
Also available in: Unified diff