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. This command is designed for simple
50 usage. For more complex use cases the commands **dsh(1)** or **cssh(1)**
51 should be used instead.
53 If the option ``-n`` is not given, the command will be executed on all
54 nodes, otherwise it will be executed only on the node(s) specified. Use
55 the option multiple times for running it on multiple nodes, like::
57 # gnt-cluster command -n node1.example.com -n node2.example.com date
59 The ``-g`` option can be used to run a command only on a specific node
62 # gnt-cluster command -g default date
64 The ``-M`` option can be used to prepend the node name to all output
65 lines. The ``--failure-only`` option hides successful commands, making
66 it easier to see failures.
68 The command is executed serially on the selected nodes. If the
69 master node is present in the list, the command will be executed
70 last on the master. Regarding the other nodes, the execution order
71 is somewhat alphabetic, so that node2.example.com will be earlier
72 than node10.example.com but after node1.example.com.
74 So given the node names node1, node2, node3, node10, node11, with
75 node3 being the master, the order will be: node1, node2, node10,
78 The command is constructed by concatenating all other command line
79 arguments. For example, to list the contents of the /etc directory
82 # gnt-cluster command ls -l /etc
84 and the command which will be executed will be ``ls -l /etc``.
89 | **copyfile** [\--use-replication-network] [-n *node*] [-g *group*]
92 Copies a file to all or to some nodes. The argument specifies the
93 source file (on the current system), the ``-n`` argument specifies
94 the target node, or nodes if the option is given multiple times. If
95 ``-n`` is not given at all, the file will be copied to all nodes. The
96 ``-g`` option can be used to only select nodes in a specific node group.
97 Passing the ``--use-replication-network`` option will cause the
98 copy to be done over the replication network (only matters if the
99 primary/secondary IPs are different). Example::
101 # gnt-cluster -n node1.example.com -n node2.example.com copyfile /tmp/test
103 This will copy the file /tmp/test from the current node to the two
109 **deactivate-master-ip** [\--yes]
111 Deactivates the master IP on the master node.
113 This should be run only locally or on a connection to the node ip
114 directly, as a connection to the master ip will be broken by this
115 operation. Because of this risk it will require user confirmation
116 unless the ``--yes`` option is passed.
121 **destroy** {\--yes-do-it}
123 Remove all configuration files related to the cluster, so that a
124 **gnt-cluster init** can be done again afterwards.
126 Since this is a dangerous command, you are required to pass the
127 argument *\--yes-do-it.*
132 **epo** [\--on] [\--groups|\--all] [\--power-delay] *arguments*
134 Performs an emergency power-off on nodes given as arguments. If
135 ``--groups`` is given, arguments are node groups. If ``--all`` is
136 provided, the whole cluster will be shut down.
138 The ``--on`` flag recovers the cluster after an emergency power-off.
139 When powering on the cluster you can use ``--power-delay`` to define the
140 time in seconds (fractions allowed) waited between powering on
143 Please note that the master node will not be turned down or up
144 automatically. It will just be left in a state, where you can manully
145 perform the shutdown of that one node. If the master is in the list of
146 affected nodes and this is not a complete cluster emergency power-off
147 (e.g. using ``--all``), you're required to do a master failover to
148 another node not affected.
155 Displays the current master node.
162 Shows runtime cluster information: cluster name, architecture (32
163 or 64 bit), master node, node list and instance list.
165 Passing the ``--roman`` option gnt-cluster info will try to print
166 its integer fields in a latin friendly way. This allows further
167 diffusion of Ganeti among ancient cultures.
173 | [{-s|\--secondary-ip} *secondary\_ip*]
174 | [\--vg-name *vg-name*]
175 | [\--master-netdev *interface-name*]
176 | [\--master-netmask *netmask*]
177 | [\--use-external-mip-script {yes \| no}]
178 | [{-m|\--mac-prefix} *mac-prefix*]
179 | [\--no-lvm-storage]
182 | [\--file-storage-dir *dir*]
183 | [\--enabled-hypervisors *hypervisors*]
184 | [{-H|\--hypervisor-parameters} *hypervisor*:*hv-param*=*value*[,*hv-param*=*value*...]]
185 | [{-B|\--backend-parameters} *be-param*=*value*[,*be-param*=*value*...]]
186 | [{-N|\--nic-parameters} *nic-param*=*value*[,*nic-param*=*value*...]]
187 | [{-D|\--disk-parameters} *disk-template*:*disk-param*=*value*[,*disk-param*=*value*...]]
188 | [\--maintain-node-health {yes \| no}]
189 | [\--uid-pool *user-id pool definition*]
190 | [{-I|\--default-iallocator} *default instance allocator*]
191 | [\--primary-ip-version *version*]
192 | [\--prealloc-wipe-disks {yes \| no}]
193 | [\--node-parameters *ndparams*]
194 | [{-C|\--candidate-pool-size} *candidate\_pool\_size*]
195 | [\--specs-cpu-count *spec-param*=*value* [,*spec-param*=*value*...]]
196 | [\--specs-disk-count *spec-param*=*value* [,*spec-param*=*value*...]]
197 | [\--specs-disk-size *spec-param*=*value* [,*spec-param*=*value*...]]
198 | [\--specs-mem-size *spec-param*=*value* [,*spec-param*=*value*...]]
199 | [\--specs-nic-count *spec-param*=*value* [,*spec-param*=*value*...]]
200 | [\--ipol-disk-templates *template* [,*template*...]]
201 | [\--disk-state *diskstate*]
202 | [\--hypervisor-state *hvstate*]
205 This commands is only run once initially on the first node of the
206 cluster. It will initialize the cluster configuration, setup the
207 ssh-keys, start the daemons on the master node, etc. in order to have
208 a working one-node cluster.
210 Note that the *clustername* is not any random name. It has to be
211 resolvable to an IP address using DNS, and it is best if you give the
212 fully-qualified domain name. This hostname must resolve to an IP
213 address reserved exclusively for this purpose, i.e. not already in
216 The cluster can run in two modes: single-home or dual-homed. In the
217 first case, all traffic (both public traffic, inter-node traffic and
218 data replication traffic) goes over the same interface. In the
219 dual-homed case, the data replication traffic goes over the second
220 network. The ``-s (--secondary-ip)`` option here marks the cluster as
221 dual-homed and its parameter represents this node's address on the
222 second network. If you initialise the cluster with ``-s``, all nodes
223 added must have a secondary IP as well.
225 Note that for Ganeti it doesn't matter if the secondary network is
226 actually a separate physical network, or is done using tunneling,
227 etc. For performance reasons, it's recommended to use a separate
230 The ``--vg-name`` option will let you specify a volume group
231 different than "xenvg" for Ganeti to use when creating instance
232 disks. This volume group must have the same name on all nodes. Once
233 the cluster is initialized this can be altered by using the
234 **modify** command. If you don't want to use lvm storage at all use
235 the ``--no-lvm-storage`` option. Once the cluster is initialized
236 you can change this setup with the **modify** command.
238 The ``--master-netdev`` option is useful for specifying a different
239 interface on which the master will activate its IP address. It's
240 important that all nodes have this interface because you'll need it
241 for a master failover.
243 The ``--master-netmask`` option allows to specify a netmask for the
244 master IP. The netmask must be specified as an integer, and will be
245 interpreted as a CIDR netmask. The default value is 32 for an IPv4
246 address and 128 for an IPv6 address.
248 The ``--use-external-mip-script`` option allows to specify whether to
249 use an user-supplied master IP address setup script, whose location is
250 ``@SYSCONFDIR@/ganeti/scripts/master-ip-setup``. If the option value is
251 set to False, the default script (located at
252 ``@PKGLIBDIR@/tools/master-ip-setup``) will be executed.
254 The ``-m (--mac-prefix)`` option will let you specify a three byte
255 prefix under which the virtual MAC addresses of your instances will be
256 generated. The prefix must be specified in the format ``XX:XX:XX`` and
257 the default is ``aa:00:00``.
259 The ``--no-lvm-storage`` option allows you to initialize the
260 cluster without lvm support. This means that only instances using
261 files as storage backend will be possible to create. Once the
262 cluster is initialized you can change this setup with the
265 The ``--no-etc-hosts`` option allows you to initialize the cluster
266 without modifying the /etc/hosts file.
268 The ``--no-ssh-init`` option allows you to initialize the cluster
269 without creating or distributing SSH key pairs.
271 The ``--file-storage-dir`` option allows you set the directory to
272 use for storing the instance disk files when using file storage as
273 backend for instance disks.
275 The ``--prealloc-wipe-disks`` sets a cluster wide configuration value
276 for wiping disks prior to allocation and size changes (``gnt-instance
277 grow-disk``). This increases security on instance level as the instance
278 can't access untouched data from its underlying storage.
280 The ``--enabled-hypervisors`` option allows you to set the list of
281 hypervisors that will be enabled for this cluster. Instance
282 hypervisors can only be chosen from the list of enabled
283 hypervisors, and the first entry of this list will be used by
284 default. Currently, the following hypervisors are available:
296 a simple chroot manager that starts chroot based on a script at the
297 root of the filesystem holding the chroot
300 fake hypervisor for development/testing
302 Either a single hypervisor name or a comma-separated list of
303 hypervisor names can be specified. If this option is not specified,
304 only the xen-pvm hypervisor is enabled by default.
306 The ``-H (--hypervisor-parameters)`` option allows you to set default
307 hypervisor specific parameters for the cluster. The format of this
308 option is the name of the hypervisor, followed by a colon and a
309 comma-separated list of key=value pairs. The keys available for each
310 hypervisors are detailed in the gnt-instance(8) man page, in the
311 **add** command plus the following parameters which are only
312 configurable globally (at cluster level):
315 Valid for the Xen PVM and KVM hypervisors.
317 This options specifies the TCP port to use for live-migration. For
318 Xen, the same port should be configured on all nodes in the
319 ``/etc/xen/xend-config.sxp`` file, under the key
320 "xend-relocation-port".
323 Valid for the KVM hypervisor.
325 This option specifies the maximum bandwidth that KVM will use for
326 instance live migrations. The value is in MiB/s.
328 This option is only effective with kvm versions >= 78 and qemu-kvm
331 The ``-B (--backend-parameters)`` option allows you to set the default
332 backend parameters for the cluster. The parameter format is a
333 comma-separated list of key=value pairs with the following supported
337 Number of VCPUs to set for an instance by default, must be an
338 integer, will be set to 1 if no specified.
341 Maximum amount of memory to allocate for an instance by default, can
342 be either an integer or an integer followed by a unit (M for
343 mebibytes and G for gibibytes are supported), will be set to 128M if
347 Minimum amount of memory to allocate for an instance by default, can
348 be either an integer or an integer followed by a unit (M for
349 mebibytes and G for gibibytes are supported), will be set to 128M if
353 Value of the auto\_balance flag for instances to use by default,
354 will be set to true if not specified.
357 Default value for the ``always\_failover`` flag for instances; if
358 not set, ``False`` is used.
361 The ``-N (--nic-parameters)`` option allows you to set the default nic
362 parameters for the cluster. The parameter format is a comma-separated
363 list of key=value pairs with the following supported keys:
366 The default nic mode, 'routed' or 'bridged'.
369 In bridged mode the default NIC bridge. In routed mode it
370 represents an hypervisor-vif-script dependent value to allow
371 different instance groups. For example under the KVM default
372 network script it is interpreted as a routing table number or
375 The ``-D (--disk-parameters)`` option allows you to set the default disk
376 template parameters at cluster level. The format used for this option is
377 similar to the one use by the ``-H`` option: the disk template name
378 must be specified first, followed by a colon and by a comma-separated
379 list of key-value pairs. These parameters can only be specified at
380 cluster and node group level; the cluster-level parameter are inherited
381 by the node group at the moment of its creation, and can be further
382 modified at node group level using the **gnt-group**(8) command.
384 The following is the list of disk parameters available for the **drbd**
385 template, with measurement units specified in square brackets at the end
386 of the description (when applicable):
389 Static re-synchronization rate. [KiB/s]
392 Number of stripes to use for data LVs.
395 Number of stripes to use for meta LVs.
398 What kind of barriers to **disable** for disks. It can either assume
399 the value "n", meaning no barrier disabled, or a non-empty string
400 containing a subset of the characters "bfd". "b" means disable disk
401 barriers, "f" means disable disk flushes, "d" disables disk drains.
404 Boolean value indicating whether the meta barriers should be
405 disabled (True) or not (False).
408 String containing the name of the default LVM volume group for DRBD
409 metadata. By default, it is set to ``xenvg``. It can be overridden
410 during the instance creation process by using the ``metavg`` key of
411 the ``--disk`` parameter.
414 String containing additional parameters to be appended to the
415 arguments list of ``drbdsetup disk``.
418 String containing additional parameters to be appended to the
419 arguments list of ``drbdsetup net``.
422 Boolean indicating whether to use the dynamic resync speed
423 controller or not. If enabled, c-plan-ahead must be non-zero and all
424 the c-* parameters will be used by DRBD. Otherwise, the value of
425 resync-rate will be used as a static resync speed.
428 Agility factor of the dynamic resync speed controller. (the higher,
429 the slower the algorithm will adapt the resync speed). A value of 0
430 (that is the default) disables the controller. [ds]
433 Maximum amount of in-flight resync data for the dynamic resync speed
434 controller. [sectors]
437 Maximum estimated peer response latency for the dynamic resync speed
441 Minimum resync speed for the dynamic resync speed controller. [KiB/s]
444 Upper bound on resync speed for the dynamic resync speed controller.
447 List of parameters available for the **plain** template:
450 Number of stripes to use for new LVs.
452 List of parameters available for the **rbd** template:
455 The RADOS cluster pool, inside which all rbd volumes will reside.
456 When a new RADOS cluster is deployed, the default pool to put rbd
457 volumes (Images in RADOS terminology) is 'rbd'.
459 The option ``--maintain-node-health`` allows one to enable/disable
460 automatic maintenance actions on nodes. Currently these include
461 automatic shutdown of instances and deactivation of DRBD devices on
462 offline nodes; in the future it might be extended to automatic
463 removal of unknown LVM volumes, etc. Note that this option is only
464 useful if the use of ``ganeti-confd`` was enabled at compilation.
466 The ``--uid-pool`` option initializes the user-id pool. The
467 *user-id pool definition* can contain a list of user-ids and/or a
468 list of user-id ranges. The parameter format is a comma-separated
469 list of numeric user-ids or user-id ranges. The ranges are defined
470 by a lower and higher boundary, separated by a dash. The boundaries
471 are inclusive. If the ``--uid-pool`` option is not supplied, the
472 user-id pool is initialized to an empty list. An empty list means
473 that the user-id pool feature is disabled.
475 The ``-I (--default-iallocator)`` option specifies the default
476 instance allocator. The instance allocator will be used for operations
477 like instance creation, instance and node migration, etc. when no
478 manual override is specified. If this option is not specified and
479 htools was not enabled at build time, the default instance allocator
480 will be blank, which means that relevant operations will require the
481 administrator to manually specify either an instance allocator, or a
482 set of nodes. If the option is not specified but htools was enabled,
483 the default iallocator will be **hail**(1) (assuming it can be found
484 on disk). The default iallocator can be changed later using the
487 The ``--primary-ip-version`` option specifies the IP version used
488 for the primary address. Possible values are 4 and 6 for IPv4 and
489 IPv6, respectively. This option is used when resolving node names
490 and the cluster name.
492 The ``--node-parameters`` option allows you to set default node
493 parameters for the cluster. Please see **ganeti**(7) for more
494 information about supported key=value pairs.
496 The ``-C (--candidate-pool-size)`` option specifies the
497 ``candidate_pool_size`` cluster parameter. This is the number of nodes
498 that the master will try to keep as master\_candidates. For more
499 details about this role and other node roles, see the ganeti(7).
501 The ``--specs-...`` and ``--ipol-disk-templates`` options specify
502 instance policy on the cluster. For the ``--specs-...`` options, each
503 option can have three values: ``min``, ``max`` and ``std``, which can
504 also be modified on group level (except for ``std``, which is defined
505 once for the entire cluster). Please note, that ``std`` values are not
506 the same as defaults set by ``--beparams``, but they are used for the
507 capacity calculations. The ``--ipol-disk-templates`` option takes a
508 comma-separated list of disk templates.
510 - ``--specs-cpu-count`` limits the number of VCPUs that can be used by an
512 - ``--specs-disk-count`` limits the number of disks
513 - ``--specs-disk-size`` limits the disk size for every disk used
514 - ``--specs-mem-size`` limits the amount of memory available
515 - ``--specs-nic-count`` sets limits on the number of NICs used
516 - ``--ipol-disk-templates`` limits the allowed disk templates
518 For details about how to use ``--hypervisor-state`` and ``--disk-state``
519 have a look at **ganeti**(7).
526 List the tags of the cluster.
531 **master-failover** [\--no-voting] [\--yes-do-it]
533 Failover the master role to the current node.
535 The ``--no-voting`` option skips the remote node agreement checks.
536 This is dangerous, but necessary in some cases (for example failing
537 over the master role in a 2 node cluster with the original master
538 down). If the original master then comes up, it won't be able to
539 start its master daemon because it won't have enough votes, but so
540 won't the new master, if the master daemon ever needs a restart.
541 You can pass ``--no-voting`` to **ganeti-masterd** on the new
542 master to solve this problem, and run **gnt-cluster redist-conf**
543 to make sure the cluster is consistent again.
545 The option ``--yes-do-it`` is used together with ``--no-voting``, for
546 skipping the interactive checks. This is even more dangerous, and should
547 only be used in conjunction with other means (e.g. a HA suite) to
548 confirm that the operation is indeed safe.
555 Checks if the master daemon is alive.
557 If the master daemon is alive and can respond to a basic query (the
558 equivalent of **gnt-cluster info**), then the exit code of the
559 command will be 0. If the master daemon is not alive (either due to
560 a crash or because this is not the master node), the exit code will
566 | **modify** [\--submit]
567 | [\--vg-name *vg-name*]
568 | [\--no-lvm-storage]
569 | [\--enabled-hypervisors *hypervisors*]
570 | [{-H|\--hypervisor-parameters} *hypervisor*:*hv-param*=*value*[,*hv-param*=*value*...]]
571 | [{-B|\--backend-parameters} *be-param*=*value*[,*be-param*=*value*...]]
572 | [{-N|\--nic-parameters} *nic-param*=*value*[,*nic-param*=*value*...]]
573 | [{-D|\--disk-parameters} *disk-template*:*disk-param*=*value*[,*disk-param*=*value*...]]
574 | [\--uid-pool *user-id pool definition*]
575 | [\--add-uids *user-id pool definition*]
576 | [\--remove-uids *user-id pool definition*]
577 | [{-C|\--candidate-pool-size} *candidate\_pool\_size*]
578 | [\--maintain-node-health {yes \| no}]
579 | [\--prealloc-wipe-disks {yes \| no}]
580 | [{-I|\--default-iallocator} *default instance allocator*]
581 | [\--reserved-lvs=*NAMES*]
582 | [\--node-parameters *ndparams*]
583 | [\--master-netdev *interface-name*]
584 | [\--master-netmask *netmask*]
585 | [\--use-external-mip-script {yes \| no}]
586 | [\--hypervisor-state *hvstate*]
587 | [\--disk-state *diskstate*]
588 | [\--specs-cpu-count *spec-param*=*value* [,*spec-param*=*value*...]]
589 | [\--specs-disk-count *spec-param*=*value* [,*spec-param*=*value*...]]
590 | [\--specs-disk-size *spec-param*=*value* [,*spec-param*=*value*...]]
591 | [\--specs-mem-size *spec-param*=*value* [,*spec-param*=*value*...]]
592 | [\--specs-nic-count *spec-param*=*value* [,*spec-param*=*value*...]]
593 | [\--ipol-disk-templates *template* [,*template*...]]
596 Modify the options for the cluster.
598 The ``--vg-name``, ``--no-lvm-storarge``, ``--enabled-hypervisors``,
599 ``-H (--hypervisor-parameters)``, ``-B (--backend-parameters)``,
600 ``-D (--disk-parameters)``, ``--nic-parameters``, ``-C
601 (--candidate-pool-size)``, ``--maintain-node-health``,
602 ``--prealloc-wipe-disks``, ``--uid-pool``, ``--node-parameters``,
603 ``--master-netdev``, ``--master-netmask`` and
604 ``--use-external-mip-script`` options are described in the **init**
607 The ``--hypervisor-state`` and ``--disk-state`` options are described in
608 detail in **ganeti(7)**.
610 The ``--add-uids`` and ``--remove-uids`` options can be used to
611 modify the user-id pool by adding/removing a list of user-ids or
614 The option ``--reserved-lvs`` specifies a list (comma-separated) of
615 logical volume group names (regular expressions) that will be
616 ignored by the cluster verify operation. This is useful if the
617 volume group used for Ganeti is shared with the system for other
618 uses. Note that it's not recommended to create and mark as ignored
619 logical volume names which match Ganeti's own name format (starting
620 with UUID and then .diskN), as this option only skips the
621 verification, but not the actual use of the names given.
623 To remove all reserved logical volumes, pass in an empty argument
624 to the option, as in ``--reserved-lvs=`` or ``--reserved-lvs ''``.
626 The ``-I (--default-iallocator)`` is described in the **init**
627 command. To clear the default iallocator, just pass an empty string
630 The ``--specs-...`` and ``--ipol-disk-templates`` options are described
631 in the **init** command.
633 See **ganeti(7)** for a description of ``--submit`` and other common
639 **queue** {drain | undrain | info}
641 Change job queue properties.
643 The ``drain`` option sets the drain flag on the job queue. No new
644 jobs will be accepted, but jobs already in the queue will be
647 The ``undrain`` will unset the drain flag on the job queue. New
648 jobs will be accepted.
650 The ``info`` option shows the properties of the job queue.
655 **watcher** {pause *duration* | continue | info}
657 Make the watcher pause or let it continue.
659 The ``pause`` option causes the watcher to pause for *duration*
662 The ``continue`` option will let the watcher continue.
664 The ``info`` option shows whether the watcher is currently paused.
669 **redist-conf** [\--submit]
671 This command forces a full push of configuration files from the
672 master node to the other nodes in the cluster. This is normally not
673 needed, but can be run if the **verify** complains about
674 configuration mismatches.
676 See **ganeti(7)** for a description of ``--submit`` and other common
682 **remove-tags** [\--from *file*] {*tag*...}
684 Remove tags from the cluster. If any of the tags are not existing
685 on the cluster, the entire operation will abort.
687 If the ``--from`` option is given, the list of tags to be removed will
688 be extended with the contents of that file (each line becomes a tag).
689 In this case, there is not need to pass tags on the command line (if
690 you do, tags from both sources will be removed). A file name of - will
691 be interpreted as stdin.
696 **rename** [-f] {*name*}
698 Renames the cluster and in the process updates the master IP
699 address to the one the new name resolves to. At least one of either
700 the name or the IP address must be different, otherwise the
701 operation will be aborted.
703 Note that since this command can be dangerous (especially when run
704 over SSH), the command will require confirmation unless run with
710 | **renew-crypto** [-f]
711 | [\--new-cluster-certificate] [\--new-confd-hmac-key]
712 | [\--new-rapi-certificate] [\--rapi-certificate *rapi-cert*]
713 | [\--new-spice-certificate | \--spice-certificate *spice-cert*
714 | \--spice-ca-certificate *spice-ca-cert*]
715 | [\--new-cluster-domain-secret] [\--cluster-domain-secret *filename*]
717 This command will stop all Ganeti daemons in the cluster and start
718 them again once the new certificates and keys are replicated. The
719 options ``--new-cluster-certificate`` and ``--new-confd-hmac-key``
720 can be used to regenerate the cluster-internal SSL certificate
721 respective the HMAC key used by ganeti-confd(8).
723 To generate a new self-signed RAPI certificate (used by
724 ganeti-rapi(8)) specify ``--new-rapi-certificate``. If you want to
725 use your own certificate, e.g. one signed by a certificate
726 authority (CA), pass its filename to ``--rapi-certificate``.
728 To generate a new self-signed SPICE certificate, used by SPICE
729 connections to the KVM hypervisor, specify the
730 ``--new-spice-certificate`` option. If you want to provide a
731 certificate, pass its filename to ``--spice-certificate`` and pass the
732 signing CA certificate to ``--spice-ca-certificate``.
734 ``--new-cluster-domain-secret`` generates a new, random cluster
735 domain secret. ``--cluster-domain-secret`` reads the secret from a
736 file. The cluster domain secret is used to sign information
737 exchanged between separate clusters via a third party.
742 **repair-disk-sizes** [instance...]
744 This command checks that the recorded size of the given instance's
745 disks matches the actual size and updates any mismatches found.
746 This is needed if the Ganeti configuration is no longer consistent
747 with reality, as it will impact some disk operations. If no
748 arguments are given, all instances will be checked.
750 Note that only active disks can be checked by this command; in case
751 a disk cannot be activated it's advised to use
752 **gnt-instance activate-disks \--ignore-size ...** to force
753 activation without regard to the current size.
755 When the all disk sizes are consistent, the command will return no
756 output. Otherwise it will log details about the inconsistencies in
762 **search-tags** {*pattern*}
764 Searches the tags on all objects in the cluster (the cluster
765 itself, the nodes and the instances) for a given pattern. The
766 pattern is interpreted as a regular expression and a search will be
767 done on it (i.e. the given pattern is not anchored to the beggining
768 of the string; if you want that, prefix the pattern with ^).
770 If no tags are matching the pattern, the exit code of the command
771 will be one. If there is at least one match, the exit code will be
772 zero. Each match is listed on one line, the object and the tag
773 separated by a space. The cluster will be listed as /cluster, a
774 node will be listed as /nodes/*name*, and an instance as
775 /instances/*name*. Example:
779 # gnt-cluster search-tags time
780 /cluster ctime:2007-09-01
781 /nodes/node1.example.com mtime:2007-10-04
786 | **verify** [\--no-nplus1-mem] [\--node-group *nodegroup*]
787 | [\--error-codes] [{-I|\--ignore-errors} *errorcode*]
788 | [{-I|\--ignore-errors} *errorcode*...]
790 Verify correctness of cluster configuration. This is safe with
791 respect to running instances, and incurs no downtime of the
794 If the ``--no-nplus1-mem`` option is given, Ganeti won't check
795 whether if it loses a node it can restart all the instances on
796 their secondaries (and report an error otherwise).
798 With ``--node-group``, restrict the verification to those nodes and
799 instances that live in the named group. This will not verify global
800 settings, but will allow to perform verification of a group while other
801 operations are ongoing in other groups.
803 The ``--error-codes`` option outputs each error in the following
804 parseable format: *ftype*:*ecode*:*edomain*:*name*:*msg*.
805 These fields have the following meaning:
808 Failure type. Can be *WARNING* or *ERROR*.
811 Error code of the failure. See below for a list of error codes.
814 Can be *cluster*, *node* or *instance*.
817 Contains the name of the item that is affected from the failure.
820 Contains a descriptive error message about the error
822 ``gnt-cluster verify`` will have a non-zero exit code if at least one of
823 the failures that are found are of type *ERROR*.
825 The ``--ignore-errors`` option can be used to change this behaviour,
826 because it demotes the error represented by the error code received as a
827 parameter to a warning. The option must be repeated for each error that
828 should be ignored (e.g.: ``-I ENODEVERSION -I ENODEORPHANLV``). The
829 ``--error-codes`` option can be used to determine the error code of a
841 The command checks which instances have degraded DRBD disks and
842 activates the disks of those instances.
844 This command is run from the **ganeti-watcher** tool, which also
845 has a different, complementary algorithm for doing this check.
846 Together, these two should ensure that DRBD disks are kept
854 Show the cluster version.
856 .. vim: set textwidth=72 :