1 <!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
3 <!-- Fill in your name for FIRSTNAME and SURNAME. -->
4 <!-- Please adjust the date whenever revising the manpage. -->
5 <!ENTITY dhdate "<date>February 12, 2009</date>">
6 <!-- SECTION should be 1-8, maybe w/ subsection other parameters are
7 allowed: see man(7), man(1). -->
8 <!ENTITY dhsection "<manvolnum>8</manvolnum>">
9 <!ENTITY dhucpackage "<refentrytitle>gnt-cluster</refentrytitle>">
10 <!ENTITY dhpackage "gnt-cluster">
12 <!ENTITY debian "<productname>Debian</productname>">
13 <!ENTITY gnu "<acronym>GNU</acronym>">
14 <!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
15 <!ENTITY footer SYSTEM "footer.sgml">
25 <holder>Google Inc.</holder>
33 <refmiscinfo>ganeti 2.0</refmiscinfo>
36 <refname>&dhpackage;</refname>
38 <refpurpose>ganeti administration, cluster-wide</refpurpose>
42 <command>&dhpackage; </command>
44 <arg choice="req">command</arg>
45 <arg>arguments...</arg>
49 <title>DESCRIPTION</title>
52 The <command>&dhpackage;</command> is used for cluster-wide
53 administration in the ganeti system.
58 <title>COMMANDS</title>
61 <title>ADD-TAGS</title>
64 <command>add-tags</command>
65 <arg choice="opt">--from <replaceable>file</replaceable></arg>
67 rep="repeat"><replaceable>tag</replaceable></arg>
71 Add tags to the cluster. If any of the tags contains invalid
72 characters, the entire operation will abort.
76 If the <option>--from</option> option is given, the list of
77 tags will be extended with the contents of that file (each
78 line becomes a tag). In this case, there is not need to pass
79 tags on the command line (if you do, both sources will be
80 used). A file name of - will be interpreted as stdin.
85 <title>COMMAND</title>
88 <command>command</command>
89 <arg>-n <replaceable>node</replaceable></arg>
90 <arg choice="req"><replaceable>command</replaceable></arg>
94 Executes a command on all nodes. If the option
95 <option>-n</option> is not given, the command will be executed
96 on all nodes, otherwise it will be executed only on the
97 node(s) specified. Use the option multiple times for running
98 it on multiple nodes, like:
101 # gnt-cluster command -n node1.example.com -n node2.example.com date
107 The command is executed serially on the selected nodes. If the
108 master node is present in the list, the command will be
109 executed last on the master. Regarding the other nodes, the
110 execution order is somewhat alphabetic, so that
111 node2.example.com will be earlier than node10.example.com but
112 after node1.example.com.
116 So given the node names node1, node2, node3, node10, node11,
117 with node3 being the master, the order will be: node1, node2,
118 node10, node11, node3.
122 The command is constructed by concatenating all other command
123 line arguments. For example, to list the contents of the
124 <filename class="directory">/etc</filename> directory on all
128 # gnt-cluster command ls -l /etc
131 and the command which will be executed will be
132 <computeroutput>"ls -l /etc"</computeroutput>
137 <title>COPYFILE</title>
140 <command>copyfile</command>
141 <arg>-n <replaceable>node</replaceable></arg>
142 <arg choice="req"><replaceable>file</replaceable></arg>
146 Copies a file to all or to some nodes. The argument specifies
147 the source file (on the current system), the
148 <option>-n</option> argument specifies the target node, or
149 nodes if the option is given multiple times. If
150 <option>-n</option> is not given at all, the file will be
155 # gnt-cluster -n node1.example.com -n node2.example.com copyfile /tmp/test
158 This will copy the file <filename>/tmp/test</filename> from
159 the current node to the two named nodes.
164 <title>DESTROY</title>
167 <command>destroy</command>
168 <arg choice="req">--yes-do-it</arg>
172 Remove all configuration files related to the cluster, so that
173 a <command>gnt-cluster init</command> can be done again
178 Since this is a dangerous command, you are required to pass
179 the argument <replaceable>--yes-do-it.</replaceable>
184 <title>GETMASTER</title>
187 <command>getmaster</command>
191 Displays the current master node.
199 <command>info</command>
203 Shows runtime cluster information: cluster name, architecture
204 (32 or 64 bit), master node, node list and instance list.
212 <command>init</command>
214 <arg>-s <replaceable>secondary_ip</replaceable></arg>
216 <arg>-b <replaceable>bridge</replaceable></arg>
218 <arg>-g <replaceable>vg-name</replaceable></arg>
220 <arg>--master-netdev <replaceable>vg-name</replaceable></arg>
222 <arg>-m <replaceable>mac-prefix</replaceable></arg>
224 <arg>--no-lvm-storage</arg>
226 <arg>--file-storage-dir <replaceable>dir</replaceable></arg>
228 <arg>--enabled-hypervisors <replaceable>hypervisors</replaceable></arg>
230 <arg>-t <replaceable>hypervisor name</replaceable></arg>
232 <arg>--hypervisor-parameters <replaceable>hv-params</replaceable></arg>
234 <arg>--backend-parameters <replaceable>be-params</replaceable></arg>
236 <arg choice="req"><replaceable>clustername</replaceable></arg>
240 This commands is only run once initially on the first node of
241 the cluster. It will initialize the cluster configuration and
242 setup ssh-keys and more.
246 Note that the <replaceable>clustername</replaceable> is not
247 any random name. It has to be resolvable to an IP address
248 using DNS, and it is best if you give the fully-qualified
249 domain name. This hostname must resolve to an IP address
250 reserved exclusively for this purpose.
254 The cluster can run in two modes: single-home or
255 dual-homed. In the first case, all traffic (both public
256 traffic, inter-node traffic and data replication traffic) goes
257 over the same interface. In the dual-homed case, the data
258 replication traffic goes over the second network. The
259 <option>-s</option> option here marks the cluster as
260 dual-homed and its parameter represents this node's address on
261 the second network. If you initialise the cluster with
262 <option>-s</option>, all nodes added must have a secondary IP
267 Note that for Ganeti it doesn't matter if the secondary
268 network is actually a separate physical network, or is done
269 using tunneling, etc. For performance reasons, it's
270 recommended to use a separate network, of course.
274 The <option>-b</option> option specifies the default bridge
279 The <option>-g</option> option will let you specify a volume group
280 different than 'xenvg' for ganeti to use when creating instance disks.
281 This volume group must have the same name on all nodes. Once the
282 cluster is initialized this can be altered by using the
283 <command>modify</command> command. If you don't want to use lvm
284 storage at all use the <option>--no-lvm-storage</option> option.
285 Once the cluster is initialized you can change this setup with the
286 <command>modify</command> command.
290 The <option>--master-netdev</option> option is useful for specifying a
291 different interface on which the master will activate its IP address.
292 It's important that all nodes have this interface because you'll need
293 it for a master failover.
297 The <option>-m</option> option will let you specify a three byte prefix
298 under which the virtual MAC addresses of your instances will be
299 generated. The prefix must be specified in the format XX:XX:XX and the
304 The <option>--no-lvm-storage</option> allows you to initialize the
305 cluster without lvm support. This means that only instances using
306 files as storage backend will be possible to create. Once the cluster
307 is initialized you can change this setup with the
308 <command>modify</command> command.
312 The <option>--file-storage-dir</option> option allows you
313 set the directory to use for storing the instance disk
314 files when using file storage as backend for instance disks.
318 The <option>--enabled-hypervisors</option> option allows you
319 to set the list of hypervisors that will be enabled for
320 this cluster. Instance hypervisors can only be choosen from
321 the list of enabled hypervisors. Currently, the following
322 hypervisors are available:
355 fake hypervisor for development/testing
363 Either a single hypervisor name or a comma-separated list of
364 hypervisor names can be specified. If this option is not
365 specified, only the xen-pvm hypervisor is enabled by default.
369 With the <option>-t</option> option, the default hypervisor
370 can be set. It has to be a member of the list of enabled
371 hypervisors. If not specified, the first entry on the list of
372 enabled hypervisors will be used by default.
376 The <option>--backend</option> option allows you to set
377 the default backend parameters for the cluster. The parameter
378 format is a comma-separated list of key=value pairs with the
379 following supported keys:
388 Number of VCPUs to set for an instance by default, must
389 be an integer, will be set to 1 if no specified.
397 Amount of memory to allocate for an instance by default,
398 can be either an integer or an integer followed by a
399 unit (M for mebibytes and G for gibibytes are
400 supported), will be set to 128M if not specified.
405 <term>auto_balance</term>
408 Value of the auto_balance flag for instances to use by
409 default, will be set to true if not specified.
417 The <option>--hypervisor-parameters</option> option allows you
418 to set default hypervisor specific parameters for the
419 cluster. The format of this option is the name of the
420 hypervisor, followed by a colon and a comma-separated list of
421 key=value pairs. The keys available for each hypervisors are
422 detailed int the <citerefentry>
423 <refentrytitle>gnt-instance</refentrytitle>
424 <manvolnum>8</manvolnum> </citerefentry> man page, in the
425 <command>add</command> command.
431 <title>LIST-TAGS</title>
434 <command>list-tags</command>
437 <para>List the tags of the cluster.</para>
441 <title>MASTERFAILOVER</title>
444 <command>masterfailover</command>
448 Failover the master role to the current node.
453 <title>MODIFY</title>
456 <command>modify</command>
458 <arg choice="opt">-g <replaceable>vg-name</replaceable></arg>
460 <arg choice="opt">--no-lvm-storage</arg>
462 <arg choice="opt">--enabled-hypervisors
463 <replaceable>hypervisors</replaceable></arg>
465 <arg choice="opt">--hypervisor-parameters
466 <replaceable>hv-params</replaceable></arg>
468 <arg choice="opt">--backend-parameters
469 <replaceable>be-params</replaceable></arg>
471 <arg>-C <replaceable>candidate_pool_size</replaceable></arg>
476 Modify the options for the cluster.
480 The <option>-g</option>, <option>--no-lvm-storarge</option>,
481 <option>--enabled-hypervisors</option>,
482 <option>--hypervisor-parameters</option> and
483 <option>--backend-parameters</option> options are
484 described in the <command>init</command> command.
488 The <option>-C</option> options specifies the
489 <varname>candidate_pool_size</varname> cluster parameter. This
490 is the number of nodes that the master will try to keep as
491 <literal>master_candidates</literal>. For more details about
492 this role and other node roles, see the <citerefentry>
493 <refentrytitle>ganeti</refentrytitle><manvolnum>7</manvolnum>
494 </citerefentry>. If you increase the size, the master will
495 automatically promote as many nodes as required and possible
496 to reach the intended number.
504 <command>queue</command>
505 <arg choice="opt">drain</arg>
506 <arg choice="opt">undrain</arg>
507 <arg choice="opt">info</arg>
512 Change job queue properties.
516 The <option>drain</option> option sets the drain flag on the
517 job queue. No new jobs will be accepted, but jobs already in
518 the queue will be processed.
522 The <option>undrain</option> will unset the drain flag on the
523 job queue. New jobs will be accepted.
527 The <option>info</option> option shows the properties of the
533 <title>redist-conf</title>
535 <command>redist-conf</command>
540 This command forces a full push of configuration files from
541 the master node to the other nodes in the cluster. This is
542 normally not needed, but can be run if the
543 <command>verify</command> complains about configuration
548 The <option>--submit</option> option is used to send the job
549 to the master daemon but not wait for its completion. The job
550 ID will be shown so that it can be examined via
551 <command>gnt-job info</command>.
556 <title>REMOVE-TAGS</title>
559 <command>remove-tags</command>
560 <arg choice="opt">--from <replaceable>file</replaceable></arg>
562 rep="repeat"><replaceable>tag</replaceable></arg>
566 Remove tags from the cluster. If any of the tags are not
567 existing on the cluster, the entire operation will abort.
571 If the <option>--from</option> option is given, the list of
572 tags will be extended with the contents of that file (each
573 line becomes a tag). In this case, there is not need to pass
574 tags on the command line (if you do, both sources will be
575 used). A file name of - will be interpreted as stdin.
580 <title>RENAME</title>
583 <command>rename</command>
585 <arg choice="req"><replaceable>name</replaceable></arg>
589 Renames the cluster and in the process updates the master IP
590 address to the one the new name resolves to. At least one of
591 either the name or the IP address must be different, otherwise
592 the operation will be aborted.
596 Note that since this command can be dangerous (especially when
597 run over SSH), the command will require confirmation unless
598 run with the <option>-f</option> option.
603 <title>SEARCH-TAGS</title>
606 <command>search-tags</command>
607 <arg choice="req"><replaceable>pattern</replaceable></arg>
611 Searches the tags on all objects in the cluster (the cluster
612 itself, the nodes and the instances) for a given pattern. The
613 pattern is interpreted as a regular expression and a search
614 will be done on it (i.e. the given pattern is not anchored to
615 the beggining of the string; if you want that, prefix the
616 pattern with <literal>^</literal>).
620 If no tags are matching the pattern, the exit code of the
621 command will be one. If there is at least one match, the exit
622 code will be zero. Each match is listed on one line, the
623 object and the tag separated by a space. The cluster will be
624 listed as <filename>/cluster</filename>, a node will be listed
626 <filename>/nodes/<replaceable>name</replaceable></filename>,
628 <filename>/instances/<replaceable>name</replaceable></filename>.
632 # gnt-cluster search time
633 /cluster ctime:2007-09-01
634 /nodes/node1.example.com mtime:2007-10-04
639 <title>VERIFY</title>
642 <command>verify</command>
643 <arg choice="opt">--no-nplus1-mem</arg>
647 Verify correctness of cluster configuration. This is safe with
648 respect to running instances, and incurs no downtime of the
653 If the <option>--no-nplus1-mem</option> option is given, ganeti won't
654 check whether if it loses a node it can restart all the instances on
655 their secondaries (and report an error otherwise).
660 <title>VERIFY-DISKS</title>
663 <command>verify-disks</command>
667 The command checks which instances have degraded DRBD disks
668 and activates the disks of those instances.
672 This command is run from the <command>ganeti-watcher</command>
673 tool, which also has a different, complementary algorithm for
674 doing this check. Together, these two should ensure that DRBD
675 disks are kept consistent.
680 <title>VERSION</title>
683 <command>version</command>
687 Show the cluster version.
697 <!-- Keep this comment at the end of the file
702 sgml-minimize-attributes:nil
703 sgml-always-quote-attributes:t
706 sgml-parent-document:nil
707 sgml-default-dtd-file:nil
708 sgml-exposed-tags:nil
709 sgml-local-catalogs:nil
710 sgml-local-ecat-files:nil