Statistics
| Branch: | Tag: | Revision:

root / man / ganeti-noded.rst @ 12f5bacf

History | View | Annotate | Download (2.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] [-p *PORT*] [-b *ADDRESS*]
13
[--no-mlock] [--syslog] [--no-ssl] [-K *SSL_KEY_FILE*] [-C *SSL_CERT_FILE*]
14

    
15
DESCRIPTION
16
-----------
17

    
18
The **ganeti-noded** is the daemon which is responsible for the
19
node functions in the Ganeti system.
20

    
21
By default, in order to be able to support features such as node
22
powercycling even on systems with a very damaged root disk,
23
**ganeti-noded** locks itself in RAM using **mlockall**\(2). You can
24
disable this feature by passing in the ``--no-mlock`` to the daemon.
25

    
26
For testing purposes, you can give the ``-f`` option and the
27
program won't detach from the running terminal.
28

    
29
Debug-level message can be activated by giving the ``-d`` option.
30

    
31
Logging to syslog, rather than its own log file, can be enabled by
32
passing in the ``--syslog`` option.
33

    
34
The **ganeti-noded** daemon listens to port 1811 TCP, on all
35
interfaces, by default. The port can be overridden by an entry in the
36
services database (usually ``/etc/services``) or by passing the ``-p``
37
option.  The ``-b`` option can be used to specify the address to bind
38
to (defaults to ``0.0.0.0``).
39

    
40
Ganeti noded communication is protected via SSL, with a key
41
generated at cluster init time. This can be disabled with the
42
``--no-ssl`` option, or a different SSL key and certificate can be
43
specified using the ``-K`` and ``-C`` options.
44

    
45
ROLE
46
~~~~
47

    
48
The role of the node daemon is to do almost all the actions that
49
change the state of the node. Things like creating disks for
50
instances, activating disks, starting/stopping instance and so on
51
are done via the node daemon.
52

    
53
Also, in some cases the startup/shutdown of the master daemon are
54
done via the node daemon, and the cluster IP address is also
55
added/removed to the master node via it.
56

    
57
If the node daemon is stopped, the instances are not affected, but
58
the master won't be able to talk to that node.
59

    
60
COMMUNICATION PROTOCOL
61
~~~~~~~~~~~~~~~~~~~~~~
62

    
63
Currently the master-node RPC is done using a simple RPC protocol
64
built using JSON over HTTP(S).
65

    
66
.. vim: set textwidth=72 :
67
.. Local Variables:
68
.. mode: rst
69
.. fill-column: 72
70
.. End: