Provided by: ganeti-2.16_2.16.0~rc2-1build1_all bug

Name

       ganeti-noded - Ganeti node daemon

Synopsis

       ganeti-noded [-f] [-d] [-p PORT] [-b ADDRESS] [-i INTERFACE]
       [--max-clients CLIENTS] [--no-mlock] [--syslog] [--no-ssl]
       [-K SSL_KEY_FILE] [-C SSL_CERT_FILE]

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  in the services database (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); alternatively, the -i option can be used to specify the interface
       to bind do.

       The maximum  number  of  simultaneous  client  connections  may  be  configured  with  the
       --max-clients  option.   This  defaults to 20.  Connections above this count are accepted,
       but no responses are sent until enough connections are closed.

       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@googlegroups.com).

SEE ALSO

       Ganeti overview and specifications: ganeti(7) (general  overview),  ganeti-os-interface(7)
       (guest OS definitions), ganeti-extstorage-interface(7) (external storage providers).

       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-storage(8) (storage 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-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),
       hinfo(1) (cluster information printer), mon-collector(7) (data collectors interface).

COPYRIGHT

       Copyright (C) 2006-2015 Google Inc.  All rights reserved.

       Redistribution  and  use  in  source  and  binary forms, with or without modification, are
       permitted provided that the following conditions are met:

       1.  Redistributions of source code must retain the above copyright notice,  this  list  of
       conditions and the following disclaimer.

       2.  Redistributions in binary form must reproduce the above copyright notice, this list of
       conditions and the following  disclaimer  in  the  documentation  and/or  other  materials
       provided with the distribution.

       THIS  SOFTWARE  IS  PROVIDED  BY  THE  COPYRIGHT  HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
       EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE  IMPLIED  WARRANTIES  OF
       MERCHANTABILITY  AND  FITNESS  FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL
       THE COPYRIGHT HOLDER OR CONTRIBUTORS BE  LIABLE  FOR  ANY  DIRECT,  INDIRECT,  INCIDENTAL,
       SPECIAL,  EXEMPLARY,  OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
       OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS  INTERRUPTION)
       HOWEVER  CAUSED  AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
       TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN  ANY  WAY  OUT  OF  THE  USE  OF  THIS
       SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.