root / man / ganeti-noded.rst @ fcdb582d
History | View | Annotate | Download (2 kB)
| 1 |
ganeti-noded(8) Ganeti | Version @GANETI_VERSION@ |
|---|---|
| 2 |
================================================= |
| 3 |
|
| 4 |
Name |
| 5 |
---- |
| 6 |
|
| 7 |
ganeti-noded - Ganeti node daemon |
| 8 |
|
| 9 |
Synopsis |
| 10 |
-------- |
| 11 |
|
| 12 |
**ganeti-noded** [-f] [-d] |
| 13 |
|
| 14 |
DESCRIPTION |
| 15 |
----------- |
| 16 |
|
| 17 |
The **ganeti-noded** is the daemon which is responsible for the |
| 18 |
node functions in the Ganeti system. |
| 19 |
|
| 20 |
By default, in order to be able to support features such as node |
| 21 |
powercycling even on systems with a very damaged root disk, |
| 22 |
**ganeti-noded** locks itself in RAM using **mlockall**(2). You can |
| 23 |
disable this feature by passing in the ``--no-mlock`` to the daemon. |
| 24 |
|
| 25 |
For testing purposes, you can give the ``-f`` option and the |
| 26 |
program won't detach from the running terminal. |
| 27 |
|
| 28 |
Debug-level message can be activated by giving the ``-d`` option. |
| 29 |
|
| 30 |
Logging to syslog, rather than its own log file, can be enabled by |
| 31 |
passing in the ``--syslog`` option. |
| 32 |
|
| 33 |
The **ganeti-noded** daemon listens to port 1811 TCP, on all |
| 34 |
interfaces, by default. This can be overridden by an entry the |
| 35 |
services database (usually /etc/services) or by passing the ``-p`` |
| 36 |
option. The ``-b`` option can be used to specify the address to bind |
| 37 |
to (defaults to ``0.0.0.0``). |
| 38 |
|
| 39 |
Ganeti noded communication is protected via SSL, with a key |
| 40 |
generated at cluster init time. This can be disabled with the |
| 41 |
``--no-ssl`` option, or a different SSL key and certificate can be |
| 42 |
specified using the ``-K`` and ``-C`` options. |
| 43 |
|
| 44 |
ROLE |
| 45 |
~~~~ |
| 46 |
|
| 47 |
The role of the node daemon is to do almost all the actions that |
| 48 |
change the state of the node. Things like creating disks for |
| 49 |
instances, activating disks, starting/stopping instance and so on |
| 50 |
are done via the node daemon. |
| 51 |
|
| 52 |
Also, in some cases the startup/shutdown of the master daemon are |
| 53 |
done via the node daemon, and the cluster IP address is also |
| 54 |
added/removed to the master node via it. |
| 55 |
|
| 56 |
If the node daemon is stopped, the instances are not affected, but |
| 57 |
the master won't be able to talk to that node. |
| 58 |
|
| 59 |
COMMUNICATION PROTOCOL |
| 60 |
~~~~~~~~~~~~~~~~~~~~~~ |
| 61 |
|
| 62 |
Currently the master-node RPC is done using a simple RPC protocol |
| 63 |
built using JSON over HTTP(S). |