ganeti-noded(8) [debian man page]
ganeti-noded(8) Version 2.5.2 ganeti-noded(8) Name ganeti-noded - Ganeti node daemon Synopsis ganeti-noded [-f] [-d] DESCRIPTION
The ganeti-noded is the daemon which is responsible for the node functions in the Ganeti system. By default, in order to be able to support features such as node powercycling even on systems with a very damaged root disk, ganeti-noded locks itself in RAM using mlockall(2). You can disable this feature by passing in the --no-mlock to the daemon. For testing purposes, you can give the -f option and the program won't detach from the running terminal. Debug-level message can be activated by giving the -d option. Logging to syslog, rather than its own log file, can be enabled by passing in the --syslog option. The ganeti-noded daemon listens to port 1811 TCP, on all interfaces, by default. The port can be overridden by an entry the services data- base (usually /etc/services) or by passing the -p option. The -b option can be used to specify the address to bind to (defaults to 0.0.0.0). Ganeti noded communication is protected via SSL, with a key generated at cluster init time. This can be disabled with the --no-ssl option, or a different SSL key and certificate can be specified using the -K and -C options. ROLE The role of the node daemon is to do almost all the actions that change the state of the node. Things like creating disks for instances, activating disks, starting/stopping instance and so on are done via the node daemon. Also, in some cases the startup/shutdown of the master daemon are done via the node daemon, and the cluster IP address is also added/removed to the master node via it. If the node daemon is stopped, the instances are not affected, but the master won't be able to talk to that node. COMMUNICATION PROTOCOL Currently the master-node RPC is done using a simple RPC protocol built using JSON over HTTP(S). REPORTING BUGS
Report bugs to project website (http://code.google.com/p/ganeti/) or contact the developers using the Ganeti mailing list (ganeti@google- groups.com). SEE ALSO
Ganeti overview and specifications: ganeti(7) (general overview), ganeti-os-interface(7) (guest OS definitions). Ganeti commands: gnt-cluster(8) (cluster-wide commands), gnt-job(8) (job-related commands), gnt-node(8) (node-related commands), gnt- instance(8) (instance commands), gnt-os(8) (guest OS commands), gnt-group(8) (node group commands), gnt-backup(8) (instance import/export commands), gnt-debug(8) (debug commands). Ganeti daemons: ganeti-watcher(8) (automatic instance restarter), ganeti-cleaner(8) (job queue cleaner), ganeti-noded(8) (node daemon), ganeti-masterd(8) (master daemon), ganeti-rapi(8) (remote API daemon). Ganeti htools: htools(1) (generic binary), hbal(1) (cluster balancer), hspace(1) (capacity calculation), hail(1) (IAllocator plugin), hscan(1) (data gatherer from remote clusters). COPYRIGHT
Copyright (C) 2006, 2007, 2008, 2009, 2010, 2011 Google Inc. Permission is granted to copy, distribute and/or modify under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. Ganeti ganeti-noded(8)
Check Out this Related Man Page
ganeti-masterd(8) Version 2.5.2 ganeti-masterd(8) Name ganeti-masterd - Ganeti master daemon Synopsis ganeti-masterd [-f] [-d] [--no-voting] DESCRIPTION
The ganeti-masterd is the daemon which is responsible for the overall cluster coordination. Without it, no change can be performed on the cluster. For testing purposes, you can give the -f option and the program won't detach from the running terminal. Debug-level message can be activated by giving the -d option. ROLE The role of the master daemon is to coordinate all the actions that change the state of the cluster. Things like accepting new jobs, coor- dinating the changes on nodes (via RPC calls to the respective node daemons), maintaining the configuration and so on are done via this daemon. The only action that can be done without the master daemon is the failover of the master role to another node in the cluster, via the gnt- cluster master-failover command. If the master daemon is stopped, the instances are not affected, but they won't be restarted automatically in case of failure. STARTUP At startup, the master daemon will confirm with the node daemons that the node it is running is indeed the master node of the cluster. It will abort if it doesn't get half plus one positive answers (offline nodes are queried too, just in case our configuration is stale). For small clusters with a number of nodes down, and especially for two-node clusters where the other has gone done, this creates a problem. In this case the --no-voting option can be used to skip this process. The option requires interactive confirmation, as having two masters on the same cluster is a very dangerous situation and will most likely lead to data loss. JOB QUEUE The master daemon maintains a job queue (located under the directory /var/lib/ganeti/queue) in which all current jobs are stored, one job per file serialized in JSON format; in this directory a subdirectory called archive holds archived job files. The moving of jobs from the current to the queue directory is done via a request to the master; this can be accomplished from the command line with the gnt-job archive or gnt-job autoarchive commands. In case of problems with the master, a job file can simply be moved away or deleted (but this might leave the cluster inconsistent). COMMUNICATION PROTOCOL The master accepts commands over a Unix socket, using JSON serialized messages separated by a specific byte sequence. For more details, see the design documentation supplied with Ganeti. REPORTING BUGS
Report bugs to project website (http://code.google.com/p/ganeti/) or contact the developers using the Ganeti mailing list (ganeti@google- groups.com). SEE ALSO
Ganeti overview and specifications: ganeti(7) (general overview), ganeti-os-interface(7) (guest OS definitions). Ganeti commands: gnt-cluster(8) (cluster-wide commands), gnt-job(8) (job-related commands), gnt-node(8) (node-related commands), gnt- instance(8) (instance commands), gnt-os(8) (guest OS commands), gnt-group(8) (node group commands), gnt-backup(8) (instance import/export commands), gnt-debug(8) (debug commands). Ganeti daemons: ganeti-watcher(8) (automatic instance restarter), ganeti-cleaner(8) (job queue cleaner), ganeti-noded(8) (node daemon), ganeti-masterd(8) (master daemon), ganeti-rapi(8) (remote API daemon). Ganeti htools: htools(1) (generic binary), hbal(1) (cluster balancer), hspace(1) (capacity calculation), hail(1) (IAllocator plugin), hscan(1) (data gatherer from remote clusters). COPYRIGHT
Copyright (C) 2006, 2007, 2008, 2009, 2010, 2011 Google Inc. Permission is granted to copy, distribute and/or modify under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. Ganeti ganeti-masterd(8)