1 gnt-cluster(8) Ganeti | Version @GANETI_VERSION@
2 ================================================
7 gnt-cluster - Ganeti administration, cluster-wide
12 **gnt-cluster** {command} [arguments...]
17 The **gnt-cluster** is used for cluster-wide administration in the
26 **activate-master-ip**
28 Activates the master IP on the master node.
33 **add-tags** [--from *file*] {*tag*...}
35 Add tags to the cluster. If any of the tags contains invalid
36 characters, the entire operation will abort.
38 If the ``--from`` option is given, the list of tags will be
39 extended with the contents of that file (each line becomes a tag).
40 In this case, there is not need to pass tags on the command line
41 (if you do, both sources will be used). A file name of - will be
47 **command** [-n *node*] [-g *group*] [-M] {*command*}
49 Executes a command on all nodes. If the option ``-n`` is not given,
50 the command will be executed on all nodes, otherwise it will be
51 executed only on the node(s) specified. Use the option multiple
52 times for running it on multiple nodes, like::
54 # gnt-cluster command -n node1.example.com -n node2.example.com date
56 The ``-g`` option can be used to run a command only on a specific node
59 # gnt-cluster command -g default date
61 The ``-M`` option can be used to prepend the node name to all output
64 The command is executed serially on the selected nodes. If the
65 master node is present in the list, the command will be executed
66 last on the master. Regarding the other nodes, the execution order
67 is somewhat alphabetic, so that node2.example.com will be earlier
68 than node10.example.com but after node1.example.com.
70 So given the node names node1, node2, node3, node10, node11, with
71 node3 being the master, the order will be: node1, node2, node10,
74 The command is constructed by concatenating all other command line
75 arguments. For example, to list the contents of the /etc directory
78 # gnt-cluster command ls -l /etc
80 and the command which will be executed will be ``ls -l /etc``.
85 | **copyfile** [--use-replication-network] [-n *node*] [-g *group*]
88 Copies a file to all or to some nodes. The argument specifies the
89 source file (on the current system), the ``-n`` argument specifies
90 the target node, or nodes if the option is given multiple times. If
91 ``-n`` is not given at all, the file will be copied to all nodes. The
92 ``-g`` option can be used to only select nodes in a specific node group.
93 Passing the ``--use-replication-network`` option will cause the
94 copy to be done over the replication network (only matters if the
95 primary/secondary IPs are different). Example::
97 # gnt-cluster -n node1.example.com -n node2.example.com copyfile /tmp/test
99 This will copy the file /tmp/test from the current node to the two
105 **deactivate-master-ip** [--yes]
107 Deactivates the master IP on the master node.
109 This should be run only locally or on a connection to the node ip
110 directly, as a connection to the master ip will be broken by this
111 operation. Because of this risk it will require user confirmation
112 unless the ``--yes`` option is passed.
117 **destroy** {--yes-do-it}
119 Remove all configuration files related to the cluster, so that a
120 **gnt-cluster init** can be done again afterwards.
122 Since this is a dangerous command, you are required to pass the
123 argument *--yes-do-it.*
128 **epo** [--on] [--groups|--all] [--power-delay] *arguments*
130 Performs an emergency power-off on nodes given as arguments. If
131 ``--groups`` is given, arguments are node groups. If ``--all`` is
132 provided, the whole cluster will be shut down.
134 The ``--on`` flag recovers the cluster after an emergency power-off.
135 When powering on the cluster you can use ``--power-delay`` to define the
136 time in seconds (fractions allowed) waited between powering on
139 Please note that the master node will not be turned down or up
140 automatically. It will just be left in a state, where you can manully
141 perform the shutdown of that one node. If the master is in the list of
142 affected nodes and this is not a complete cluster emergency power-off
143 (e.g. using ``--all``), you're required to do a master failover to
144 another node not affected.
151 Displays the current master node.
158 Shows runtime cluster information: cluster name, architecture (32
159 or 64 bit), master node, node list and instance list.
161 Passing the ``--roman`` option gnt-cluster info will try to print
162 its integer fields in a latin friendly way. This allows further
163 diffusion of Ganeti among ancient cultures.
169 | [{-s|--secondary-ip} *secondary\_ip*]
170 | [--vg-name *vg-name*]
171 | [--master-netdev *interface-name*]
172 | [--master-netmask *netmask*]
173 | [--use-external-mip-script {yes \| no}]
174 | [{-m|--mac-prefix} *mac-prefix*]
178 | [--file-storage-dir *dir*]
179 | [--enabled-hypervisors *hypervisors*]
180 | [{-H|--hypervisor-parameters} *hypervisor*:*hv-param*=*value*[,*hv-param*=*value*...]]
181 | [{-B|--backend-parameters} *be-param*=*value*[,*be-param*=*value*...]]
182 | [{-N|--nic-parameters} *nic-param*=*value*[,*nic-param*=*value*...]]
183 | [{-D|--disk-parameters} *disk-template*:*disk-param*=*value*[,*disk-param*=*value*...]]
184 | [--maintain-node-health {yes \| no}]
185 | [--uid-pool *user-id pool definition*]
186 | [{-I|--default-iallocator} *default instance allocator*]
187 | [--primary-ip-version *version*]
188 | [--prealloc-wipe-disks {yes \| no}]
189 | [--node-parameters *ndparams*]
190 | [{-C|--candidate-pool-size} *candidate\_pool\_size*]
191 | [--specs-cpu-count *spec-param*=*value* [,*spec-param*=*value*...]]
192 | [--specs-disk-count *spec-param*=*value* [,*spec-param*=*value*...]]
193 | [--specs-disk-size *spec-param*=*value* [,*spec-param*=*value*...]]
194 | [--specs-mem-size *spec-param*=*value* [,*spec-param*=*value*...]]
195 | [--specs-nic-count *spec-param*=*value* [,*spec-param*=*value*...]]
196 | [--specs-disk-templates *template* [,*template*...]]
197 | [--disk-state *diskstate*]
198 | [--hypervisor-state *hvstate*]
201 This commands is only run once initially on the first node of the
202 cluster. It will initialize the cluster configuration, setup the
203 ssh-keys, start the daemons on the master node, etc. in order to have
204 a working one-node cluster.
206 Note that the *clustername* is not any random name. It has to be
207 resolvable to an IP address using DNS, and it is best if you give the
208 fully-qualified domain name. This hostname must resolve to an IP
209 address reserved exclusively for this purpose, i.e. not already in
212 The cluster can run in two modes: single-home or dual-homed. In the
213 first case, all traffic (both public traffic, inter-node traffic and
214 data replication traffic) goes over the same interface. In the
215 dual-homed case, the data replication traffic goes over the second
216 network. The ``-s (--secondary-ip)`` option here marks the cluster as
217 dual-homed and its parameter represents this node's address on the
218 second network. If you initialise the cluster with ``-s``, all nodes
219 added must have a secondary IP as well.
221 Note that for Ganeti it doesn't matter if the secondary network is
222 actually a separate physical network, or is done using tunneling,
223 etc. For performance reasons, it's recommended to use a separate
226 The ``--vg-name`` option will let you specify a volume group
227 different than "xenvg" for Ganeti to use when creating instance
228 disks. This volume group must have the same name on all nodes. Once
229 the cluster is initialized this can be altered by using the
230 **modify** command. If you don't want to use lvm storage at all use
231 the ``--no-lvm-storage`` option. Once the cluster is initialized
232 you can change this setup with the **modify** command.
234 The ``--master-netdev`` option is useful for specifying a different
235 interface on which the master will activate its IP address. It's
236 important that all nodes have this interface because you'll need it
237 for a master failover.
239 The ``--master-netmask`` option allows to specify a netmask for the
240 master IP. The netmask must be specified as an integer, and will be
241 interpreted as a CIDR netmask. The default value is 32 for an IPv4
242 address and 128 for an IPv6 address.
244 The ``--use-external-mip-script`` options allows to specify
245 whether to use an user-supplied master IP address setup script, whose
246 location is ``/etc/ganeti/scripts/master-ip-setup``. If the option value
247 is set to False, the default script, whose location is
248 ``/usr/local/lib/ganeti/tools/master-ip-setup``, will be executed.
250 The ``-m (--mac-prefix)`` option will let you specify a three byte
251 prefix under which the virtual MAC addresses of your instances will be
252 generated. The prefix must be specified in the format ``XX:XX:XX`` and
253 the default is ``aa:00:00``.
255 The ``--no-lvm-storage`` option allows you to initialize the
256 cluster without lvm support. This means that only instances using
257 files as storage backend will be possible to create. Once the
258 cluster is initialized you can change this setup with the
261 The ``--no-etc-hosts`` option allows you to initialize the cluster
262 without modifying the /etc/hosts file.
264 The ``--no-ssh-init`` option allows you to initialize the cluster
265 without creating or distributing SSH key pairs.
267 The ``--file-storage-dir`` option allows you set the directory to
268 use for storing the instance disk files when using file storage as
269 backend for instance disks.
271 The ``--prealloc-wipe-disks`` sets a cluster wide configuration
272 value for wiping disks prior to allocation. This increases security
273 on instance level as the instance can't access untouched data from
274 it's underlying storage.
276 The ``--enabled-hypervisors`` option allows you to set the list of
277 hypervisors that will be enabled for this cluster. Instance
278 hypervisors can only be chosen from the list of enabled
279 hypervisors, and the first entry of this list will be used by
280 default. Currently, the following hypervisors are available:
292 a simple chroot manager that starts chroot based on a script at the
293 root of the filesystem holding the chroot
296 fake hypervisor for development/testing
298 Either a single hypervisor name or a comma-separated list of
299 hypervisor names can be specified. If this option is not specified,
300 only the xen-pvm hypervisor is enabled by default.
302 The ``-H (--hypervisor-parameters)`` option allows you to set default
303 hypervisor specific parameters for the cluster. The format of this
304 option is the name of the hypervisor, followed by a colon and a
305 comma-separated list of key=value pairs. The keys available for each
306 hypervisors are detailed in the gnt-instance(8) man page, in the
307 **add** command plus the following parameters which are only
308 configurable globally (at cluster level):
311 Valid for the Xen PVM and KVM hypervisors.
313 This options specifies the TCP port to use for live-migration. For
314 Xen, the same port should be configured on all nodes in the
315 ``/etc/xen/xend-config.sxp`` file, under the key
316 "xend-relocation-port".
319 Valid for the KVM hypervisor.
321 This option specifies the maximum bandwidth that KVM will use for
322 instance live migrations. The value is in MiB/s.
324 This option is only effective with kvm versions >= 78 and qemu-kvm
327 The ``-B (--backend-parameters)`` option allows you to set the default
328 backend parameters for the cluster. The parameter format is a
329 comma-separated list of key=value pairs with the following supported
333 Number of VCPUs to set for an instance by default, must be an
334 integer, will be set to 1 if no specified.
337 Maximum amount of memory to allocate for an instance by default, can
338 be either an integer or an integer followed by a unit (M for
339 mebibytes and G for gibibytes are supported), will be set to 128M if
343 Minimum amount of memory to allocate for an instance by default, can
344 be either an integer or an integer followed by a unit (M for
345 mebibytes and G for gibibytes are supported), will be set to 128M if
349 Value of the auto\_balance flag for instances to use by default,
350 will be set to true if not specified.
353 Default value for the ``always\_failover`` flag for instances; if
354 not set, ``False`` is used.
357 The ``-N (--nic-parameters)`` option allows you to set the default nic
358 parameters for the cluster. The parameter format is a comma-separated
359 list of key=value pairs with the following supported keys:
362 The default nic mode, 'routed' or 'bridged'.
365 In bridged mode the default NIC bridge. In routed mode it
366 represents an hypervisor-vif-script dependent value to allow
367 different instance groups. For example under the KVM default
368 network script it is interpreted as a routing table number or
371 The ``-D (--disk-parameters)`` option allows you to set the default disk
372 template parameters at cluster level. The format used for this option is
373 similar to the one use by the ``-H`` option: the disk template name
374 must be specified first, followed by a colon and by a comma-separated
375 list of key-value pairs. These parameters can only be specified at
376 cluster and node group level; the cluster-level parameter are inherited
377 by the node group at the moment of its creation, and can be further
378 modified at node group level using the **gnt-group**(8) command.
380 The following is the list of disk parameters available for the **drbd**
381 template, with measurement units specified in square brackets at the end
382 of the description (when applicable):
385 Static re-synchronization rate. [KiB/s]
388 Number of stripes to use for data LVs.
391 Number of stripes to use for meta LVs.
394 What kind of barriers to **disable** for disks. It can either assume
395 the value "n", meaning no barrier disabled, or a non-empty string
396 containing a subset of the characters "bfd". "b" means disable disk
397 barriers, "f" means disable disk flushes, "d" disables disk drains.
400 Boolean value indicating whether the meta barriers should be
401 disabled (True) or not (False).
404 String containing the name of the default LVM volume group for DRBD
405 metadata. By default, it is set to ``xenvg``. It can be overridden
406 during the instance creation process by using the ``metavg`` key of
407 the ``--disk`` parameter.
410 String containing additional parameters to be appended to the
411 arguments list of ``drbdsetup disk``.
414 String containing additional parameters to be appended to the
415 arguments list of ``drbdsetup net``.
418 Boolean indicating whether to use the dynamic resync speed
419 controller or not. If enabled, c-plan-ahead must be non-zero and all
420 the c-* parameters will be used by DRBD. Otherwise, the value of
421 resync-rate will be used as a static resync speed.
424 Agility factor of the dynamic resync speed controller. (the higher,
425 the slower the algorithm will adapt the resync speed). A value of 0
426 (that is the default) disables the controller. [ds]
429 Maximum amount of in-flight resync data for the dynamic resync speed
430 controller. [sectors]
433 Maximum estimated peer response latency for the dynamic resync speed
437 Minimum resync speed for the dynamic resync speed controller. [KiB/s]
440 Upper bound on resync speed for the dynamic resync speed controller.
443 List of parameters available for the **plain** template:
446 Number of stripes to use for new LVs.
448 The option ``--maintain-node-health`` allows one to enable/disable
449 automatic maintenance actions on nodes. Currently these include
450 automatic shutdown of instances and deactivation of DRBD devices on
451 offline nodes; in the future it might be extended to automatic
452 removal of unknown LVM volumes, etc. Note that this option is only
453 useful if the use of ``ganeti-confd`` was enabled at compilation.
455 The ``--uid-pool`` option initializes the user-id pool. The
456 *user-id pool definition* can contain a list of user-ids and/or a
457 list of user-id ranges. The parameter format is a comma-separated
458 list of numeric user-ids or user-id ranges. The ranges are defined
459 by a lower and higher boundary, separated by a dash. The boundaries
460 are inclusive. If the ``--uid-pool`` option is not supplied, the
461 user-id pool is initialized to an empty list. An empty list means
462 that the user-id pool feature is disabled.
464 The ``-I (--default-iallocator)`` option specifies the default
465 instance allocator. The instance allocator will be used for operations
466 like instance creation, instance and node migration, etc. when no
467 manual override is specified. If this option is not specified and
468 htools was not enabled at build time, the default instance allocator
469 will be blank, which means that relevant operations will require the
470 administrator to manually specify either an instance allocator, or a
471 set of nodes. If the option is not specified but htools was enabled,
472 the default iallocator will be **hail**(1) (assuming it can be found
473 on disk). The default iallocator can be changed later using the
476 The ``--primary-ip-version`` option specifies the IP version used
477 for the primary address. Possible values are 4 and 6 for IPv4 and
478 IPv6, respectively. This option is used when resolving node names
479 and the cluster name.
481 The ``--node-parameters`` option allows you to set default node
482 parameters for the cluster. Please see **ganeti**(7) for more
483 information about supported key=value pairs.
485 The ``-C (--candidate-pool-size)`` option specifies the
486 ``candidate_pool_size`` cluster parameter. This is the number of nodes
487 that the master will try to keep as master\_candidates. For more
488 details about this role and other node roles, see the ganeti(7).
490 The ``--specs-...`` options specify instance policy on the
491 cluster. Except for the ``disk-templates`` option, each option can have
492 three values: ``min``, ``max`` and ``std``, which can also be modified
493 on group level (except for ``std``, which is defined once for the entire
494 cluster). Please note, that ``std`` values are not the same as defaults
495 set by ``--beparams``, but they are used for the capacity calculations.
497 - ``--specs-cpu-count`` limits the number of VCPUs that can be used by an
499 - ``--specs-disk-count`` limits the number of disks
500 - ``--specs-disk-size`` limits the disk size for every disk used
501 - ``--specs-mem-size`` limits the amount of memory available
502 - ``--specs-nic-count`` sets limits on the number of NICs used
503 - ``--specs-disk-templates`` limits the allowed disk templates (no
504 mix/std/max for this option)
506 For details about how to use ``--hypervisor-state`` and ``--disk-state``
507 have a look at **ganeti**(7).
514 List the tags of the cluster.
519 **master-failover** [--no-voting]
521 Failover the master role to the current node.
523 The ``--no-voting`` option skips the remote node agreement checks.
524 This is dangerous, but necessary in some cases (for example failing
525 over the master role in a 2 node cluster with the original master
526 down). If the original master then comes up, it won't be able to
527 start its master daemon because it won't have enough votes, but so
528 won't the new master, if the master daemon ever needs a restart.
529 You can pass ``--no-voting`` to **ganeti-masterd** on the new
530 master to solve this problem, and run **gnt-cluster redist-conf**
531 to make sure the cluster is consistent again.
538 Checks if the master daemon is alive.
540 If the master daemon is alive and can respond to a basic query (the
541 equivalent of **gnt-cluster info**), then the exit code of the
542 command will be 0. If the master daemon is not alive (either due to
543 a crash or because this is not the master node), the exit code will
550 | [--vg-name *vg-name*]
552 | [--enabled-hypervisors *hypervisors*]
553 | [{-H|--hypervisor-parameters} *hypervisor*:*hv-param*=*value*[,*hv-param*=*value*...]]
554 | [{-B|--backend-parameters} *be-param*=*value*[,*be-param*=*value*...]]
555 | [{-N|--nic-parameters} *nic-param*=*value*[,*nic-param*=*value*...]]
556 | [{-D|--disk-parameters} *disk-template*:*disk-param*=*value*[,*disk-param*=*value*...]]
557 | [--uid-pool *user-id pool definition*]
558 | [--add-uids *user-id pool definition*]
559 | [--remove-uids *user-id pool definition*]
560 | [{-C|--candidate-pool-size} *candidate\_pool\_size*]
561 | [--maintain-node-health {yes \| no}]
562 | [--prealloc-wipe-disks {yes \| no}]
563 | [{-I|--default-iallocator} *default instance allocator*]
564 | [--reserved-lvs=*NAMES*]
565 | [--node-parameters *ndparams*]
566 | [--master-netdev *interface-name*]
567 | [--master-netmask *netmask*]
568 | [--use-external-mip-script {yes \| no}]
569 | [--hypervisor-state *hvstate*]
570 | [--disk-state *diskstate*]
571 | [--specs-cpu-count *spec-param*=*value* [,*spec-param*=*value*...]]
572 | [--specs-disk-count *spec-param*=*value* [,*spec-param*=*value*...]]
573 | [--specs-disk-size *spec-param*=*value* [,*spec-param*=*value*...]]
574 | [--specs-mem-size *spec-param*=*value* [,*spec-param*=*value*...]]
575 | [--specs-nic-count *spec-param*=*value* [,*spec-param*=*value*...]]
576 | [--specs-disk-templates *template* [,*template*...]]
579 Modify the options for the cluster.
581 The ``--vg-name``, ``--no-lvm-storarge``, ``--enabled-hypervisors``,
582 ``-H (--hypervisor-parameters)``, ``-B (--backend-parameters)``,
583 ``-D (--disk-parameters)``, ``--nic-parameters``, ``-C
584 (--candidate-pool-size)``, ``--maintain-node-health``,
585 ``--prealloc-wipe-disks``, ``--uid-pool``, ``--node-parameters``,
586 ``--master-netdev``, ``--master-netmask`` and
587 ``--use-external-mip-script`` options are described in the **init**
590 The ``--hypervisor-state`` and ``--disk-state`` options are described in
591 detail in **ganeti**(7).
593 The ``--add-uids`` and ``--remove-uids`` options can be used to
594 modify the user-id pool by adding/removing a list of user-ids or
597 The option ``--reserved-lvs`` specifies a list (comma-separated) of
598 logical volume group names (regular expressions) that will be
599 ignored by the cluster verify operation. This is useful if the
600 volume group used for Ganeti is shared with the system for other
601 uses. Note that it's not recommended to create and mark as ignored
602 logical volume names which match Ganeti's own name format (starting
603 with UUID and then .diskN), as this option only skips the
604 verification, but not the actual use of the names given.
606 To remove all reserved logical volumes, pass in an empty argument
607 to the option, as in ``--reserved-lvs=`` or ``--reserved-lvs ''``.
609 The ``-I (--default-iallocator)`` is described in the **init**
610 command. To clear the default iallocator, just pass an empty string
613 The ``--specs-...`` options are described in the **init** command.
618 **queue** {drain | undrain | info}
620 Change job queue properties.
622 The ``drain`` option sets the drain flag on the job queue. No new
623 jobs will be accepted, but jobs already in the queue will be
626 The ``undrain`` will unset the drain flag on the job queue. New
627 jobs will be accepted.
629 The ``info`` option shows the properties of the job queue.
634 **watcher** {pause *duration* | continue | info}
636 Make the watcher pause or let it continue.
638 The ``pause`` option causes the watcher to pause for *duration*
641 The ``continue`` option will let the watcher continue.
643 The ``info`` option shows whether the watcher is currently paused.
648 **redist-conf** [--submit]
650 This command forces a full push of configuration files from the
651 master node to the other nodes in the cluster. This is normally not
652 needed, but can be run if the **verify** complains about
653 configuration mismatches.
655 The ``--submit`` option is used to send the job to the master
656 daemon but not wait for its completion. The job ID will be shown so
657 that it can be examined via **gnt-job info**.
662 **remove-tags** [--from *file*] {*tag*...}
664 Remove tags from the cluster. If any of the tags are not existing
665 on the cluster, the entire operation will abort.
667 If the ``--from`` option is given, the list of tags to be removed will
668 be extended with the contents of that file (each line becomes a tag).
669 In this case, there is not need to pass tags on the command line (if
670 you do, tags from both sources will be removed). A file name of - will
671 be interpreted as stdin.
676 **rename** [-f] {*name*}
678 Renames the cluster and in the process updates the master IP
679 address to the one the new name resolves to. At least one of either
680 the name or the IP address must be different, otherwise the
681 operation will be aborted.
683 Note that since this command can be dangerous (especially when run
684 over SSH), the command will require confirmation unless run with
690 | **renew-crypto** [-f]
691 | [--new-cluster-certificate] [--new-confd-hmac-key]
692 | [--new-rapi-certificate] [--rapi-certificate *rapi-cert*]
693 | [--new-spice-certificate | --spice-certificate *spice-cert*
694 | -- spice-ca-certificate *spice-ca-cert*]
695 | [--new-cluster-domain-secret] [--cluster-domain-secret *filename*]
697 This command will stop all Ganeti daemons in the cluster and start
698 them again once the new certificates and keys are replicated. The
699 options ``--new-cluster-certificate`` and ``--new-confd-hmac-key``
700 can be used to regenerate the cluster-internal SSL certificate
701 respective the HMAC key used by ganeti-confd(8).
703 To generate a new self-signed RAPI certificate (used by
704 ganeti-rapi(8)) specify ``--new-rapi-certificate``. If you want to
705 use your own certificate, e.g. one signed by a certificate
706 authority (CA), pass its filename to ``--rapi-certificate``.
708 To generate a new self-signed SPICE certificate, used by SPICE
709 connections to the KVM hypervisor, specify the
710 ``--new-spice-certificate`` option. If you want to provide a
711 certificate, pass its filename to ``--spice-certificate`` and pass the
712 signing CA certificate to ``--spice-ca-certificate``.
714 ``--new-cluster-domain-secret`` generates a new, random cluster
715 domain secret. ``--cluster-domain-secret`` reads the secret from a
716 file. The cluster domain secret is used to sign information
717 exchanged between separate clusters via a third party.
722 **repair-disk-sizes** [instance...]
724 This command checks that the recorded size of the given instance's
725 disks matches the actual size and updates any mismatches found.
726 This is needed if the Ganeti configuration is no longer consistent
727 with reality, as it will impact some disk operations. If no
728 arguments are given, all instances will be checked.
730 Note that only active disks can be checked by this command; in case
731 a disk cannot be activated it's advised to use
732 **gnt-instance activate-disks --ignore-size ...** to force
733 activation without regard to the current size.
735 When the all disk sizes are consistent, the command will return no
736 output. Otherwise it will log details about the inconsistencies in
742 **search-tags** {*pattern*}
744 Searches the tags on all objects in the cluster (the cluster
745 itself, the nodes and the instances) for a given pattern. The
746 pattern is interpreted as a regular expression and a search will be
747 done on it (i.e. the given pattern is not anchored to the beggining
748 of the string; if you want that, prefix the pattern with ^).
750 If no tags are matching the pattern, the exit code of the command
751 will be one. If there is at least one match, the exit code will be
752 zero. Each match is listed on one line, the object and the tag
753 separated by a space. The cluster will be listed as /cluster, a
754 node will be listed as /nodes/*name*, and an instance as
755 /instances/*name*. Example:
759 # gnt-cluster search-tags time
760 /cluster ctime:2007-09-01
761 /nodes/node1.example.com mtime:2007-10-04
766 | **verify** [--no-nplus1-mem] [--node-group *nodegroup*]
767 | [--error-codes] [{-I|--ignore-errors} *errorcode*]
768 | [{-I|--ignore-errors} *errorcode*...]
770 Verify correctness of cluster configuration. This is safe with
771 respect to running instances, and incurs no downtime of the
774 If the ``--no-nplus1-mem`` option is given, Ganeti won't check
775 whether if it loses a node it can restart all the instances on
776 their secondaries (and report an error otherwise).
778 With ``--node-group``, restrict the verification to those nodes and
779 instances that live in the named group. This will not verify global
780 settings, but will allow to perform verification of a group while other
781 operations are ongoing in other groups.
783 The ``--error-codes`` option outputs each error in the following
784 parseable format: *ftype*:*ecode*:*edomain*:*name*:*msg*.
785 These fields have the following meaning:
788 Failure type. Can be *WARNING* or *ERROR*.
791 Error code of the failure. See below for a list of error codes.
794 Can be *cluster*, *node* or *instance*.
797 Contains the name of the item that is affected from the failure.
800 Contains a descriptive error message about the error
802 ``gnt-cluster verify`` will have a non-zero exit code if at least one of
803 the failures that are found are of type *ERROR*.
805 The ``--ignore-errors`` option can be used to change this behaviour,
806 because it demotes the error represented by the error code received as a
807 parameter to a warning. The option must be repeated for each error that
808 should be ignored (e.g.: ``-I ENODEVERSION -I ENODEORPHANLV``). The
809 ``--error-codes`` option can be used to determine the error code of a
821 The command checks which instances have degraded DRBD disks and
822 activates the disks of those instances.
824 This command is run from the **ganeti-watcher** tool, which also
825 has a different, complementary algorithm for doing this check.
826 Together, these two should ensure that DRBD disks are kept
834 Show the cluster version.
836 .. vim: set textwidth=72 :