Statistics
| Branch: | Tag: | Revision:

root / man / gnt-cluster.rst @ 90bb3fe1

History | View | Annotate | Download (24.8 kB)

1
gnt-cluster(8) Ganeti | Version @GANETI_VERSION@
2
================================================
3

    
4
Name
5
----
6

    
7
gnt-cluster - Ganeti administration, cluster-wide
8

    
9
Synopsis
10
--------
11

    
12
**gnt-cluster** {command} [arguments...]
13

    
14
DESCRIPTION
15
-----------
16

    
17
The **gnt-cluster** is used for cluster-wide administration in the
18
Ganeti system.
19

    
20
COMMANDS
21
--------
22

    
23
ACTIVATE-MASTER-IP
24
~~~~~~~~~~~~~~~~~~
25

    
26
**activate-master-ip**
27

    
28
Activates the master IP on the master node.
29

    
30
ADD-TAGS
31
~~~~~~~~
32

    
33
**add-tags** [--from *file*] {*tag*...}
34

    
35
Add tags to the cluster. If any of the tags contains invalid
36
characters, the entire operation will abort.
37

    
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
42
interpreted as stdin.
43

    
44
COMMAND
45
~~~~~~~
46

    
47
**command** [-n *node*] [-g *group*] {*command*}
48

    
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::
53

    
54
    # gnt-cluster command -n node1.example.com -n node2.example.com date
55

    
56
The ``-g`` option can be used to run a command only on a specific node
57
group, e.g.::
58

    
59
    # gnt-cluster command -g default date
60

    
61
The command is executed serially on the selected nodes. If the
62
master node is present in the list, the command will be executed
63
last on the master. Regarding the other nodes, the execution order
64
is somewhat alphabetic, so that node2.example.com will be earlier
65
than node10.example.com but after node1.example.com.
66

    
67
So given the node names node1, node2, node3, node10, node11, with
68
node3 being the master, the order will be: node1, node2, node10,
69
node11, node3.
70

    
71
The command is constructed by concatenating all other command line
72
arguments. For example, to list the contents of the /etc directory
73
on all nodes, run::
74

    
75
    # gnt-cluster command ls -l /etc
76

    
77
and the command which will be executed will be ``ls -l /etc``.
78

    
79
COPYFILE
80
~~~~~~~~
81

    
82
| **copyfile** [--use-replication-network] [-n *node*] [-g *group*]
83
| {*file*}
84

    
85
Copies a file to all or to some nodes. The argument specifies the
86
source file (on the current system), the ``-n`` argument specifies
87
the target node, or nodes if the option is given multiple times. If
88
``-n`` is not given at all, the file will be copied to all nodes. The
89
``-g`` option can be used to only select nodes in a specific node group.
90
Passing the ``--use-replication-network`` option will cause the
91
copy to be done over the replication network (only matters if the
92
primary/secondary IPs are different). Example::
93

    
94
    # gnt-cluster -n node1.example.com -n node2.example.com copyfile /tmp/test
95

    
96
This will copy the file /tmp/test from the current node to the two
97
named nodes.
98

    
99
DEACTIVATE-MASTER-IP
100
~~~~~~~~~~~~~~~~~~~~
101

    
102
**deactivate-master-ip** [--yes]
103

    
104
Deactivates the master IP on the master node.
105

    
106
This should be run only locally or on a connection to the node ip
107
directly, as a connection to the master ip will be broken by this
108
operation. Because of this risk it will require user confirmation
109
unless the ``--yes`` option is passed.
110

    
111
DESTROY
112
~~~~~~~
113

    
114
**destroy** {--yes-do-it}
115

    
116
Remove all configuration files related to the cluster, so that a
117
**gnt-cluster init** can be done again afterwards.
118

    
119
Since this is a dangerous command, you are required to pass the
120
argument *--yes-do-it.*
121

    
122
EPO
123
~~~
124

    
125
**epo** [--on] [--groups|--all] [--power-delay] *arguments*
126

    
127
Performs an emergency power-off on nodes given as arguments. If
128
``--groups`` is given, arguments are node groups. If ``--all`` is
129
provided, the whole cluster will be shut down.
130

    
131
The ``--on`` flag recovers the cluster after an emergency power-off.
132
When powering on the cluster you can use ``--power-delay`` to define the
133
time in seconds (fractions allowed) waited between powering on
134
individual nodes.
135

    
136
Please note that the master node will not be turned down or up
137
automatically.  It will just be left in a state, where you can manully
138
perform the shutdown of that one node. If the master is in the list of
139
affected nodes and this is not a complete cluster emergency power-off
140
(e.g. using ``--all``), you're required to do a master failover to
141
another node not affected.
142

    
143
GETMASTER
144
~~~~~~~~~
145

    
146
**getmaster**
147

    
148
Displays the current master node.
149

    
150
INFO
151
~~~~
152

    
153
**info** [--roman]
154

    
155
Shows runtime cluster information: cluster name, architecture (32
156
or 64 bit), master node, node list and instance list.
157

    
158
Passing the ``--roman`` option gnt-cluster info will try to print
159
its integer fields in a latin friendly way. This allows further
160
diffusion of Ganeti among ancient cultures.
161

    
162
INIT
163
~~~~
164

    
165
| **init**
166
| [{-s|--secondary-ip} *secondary\_ip*]
167
| [--vg-name *vg-name*]
168
| [--master-netdev *interface-name*]
169
| [--master-netmask *netmask*]
170
| [--use-external-mip-script {yes \| no}]
171
| [{-m|--mac-prefix} *mac-prefix*]
172
| [--no-lvm-storage]
173
| [--no-etc-hosts]
174
| [--no-ssh-init]
175
| [--file-storage-dir *dir*]
176
| [--enabled-hypervisors *hypervisors*]
177
| [{-H|--hypervisor-parameters} *hypervisor*:*hv-param*=*value*[,*hv-param*=*value*...]]
178
| [{-B|--backend-parameters} *be-param*=*value* [,*be-param*=*value*...]]
179
| [{-N|--nic-parameters} *nic-param*=*value* [,*nic-param*=*value*...]]
180
| [--maintain-node-health {yes \| no}]
181
| [--uid-pool *user-id pool definition*]
182
| [{-I|--default-iallocator} *default instance allocator*]
183
| [--primary-ip-version *version*]
184
| [--prealloc-wipe-disks {yes \| no}]
185
| [--node-parameters *ndparams*]
186
| [{-C|--candidate-pool-size} *candidate\_pool\_size*]
187
| {*clustername*}
188

    
189
This commands is only run once initially on the first node of the
190
cluster. It will initialize the cluster configuration, setup the
191
ssh-keys, start the daemons on the master node, etc. in order to have
192
a working one-node cluster.
193

    
194
Note that the *clustername* is not any random name. It has to be
195
resolvable to an IP address using DNS, and it is best if you give the
196
fully-qualified domain name. This hostname must resolve to an IP
197
address reserved exclusively for this purpose, i.e. not already in
198
use.
199

    
200
The cluster can run in two modes: single-home or dual-homed. In the
201
first case, all traffic (both public traffic, inter-node traffic and
202
data replication traffic) goes over the same interface. In the
203
dual-homed case, the data replication traffic goes over the second
204
network. The ``-s (--secondary-ip)`` option here marks the cluster as
205
dual-homed and its parameter represents this node's address on the
206
second network.  If you initialise the cluster with ``-s``, all nodes
207
added must have a secondary IP as well.
208

    
209
Note that for Ganeti it doesn't matter if the secondary network is
210
actually a separate physical network, or is done using tunneling,
211
etc. For performance reasons, it's recommended to use a separate
212
network, of course.
213

    
214
The ``--vg-name`` option will let you specify a volume group
215
different than "xenvg" for Ganeti to use when creating instance
216
disks. This volume group must have the same name on all nodes. Once
217
the cluster is initialized this can be altered by using the
218
**modify** command. If you don't want to use lvm storage at all use
219
the ``--no-lvm-storage`` option. Once the cluster is initialized
220
you can change this setup with the **modify** command.
221

    
222
The ``--master-netdev`` option is useful for specifying a different
223
interface on which the master will activate its IP address. It's
224
important that all nodes have this interface because you'll need it
225
for a master failover.
226

    
227
The ``--master-netmask`` option allows to specify a netmask for the
228
master IP. The netmask must be specified as an integer, and will be
229
interpreted as a CIDR netmask. The default value is 32 for an IPv4
230
address and 128 for an IPv6 address.
231

    
232
The ``--use-external-mip-script`` options allows to specify
233
whether to use an user-supplied master IP address setup script, whose
234
location is ``/etc/ganeti/scripts/master-ip-setup``. If the option value
235
is set to False, the default script, whose location is
236
``/usr/local/lib/ganeti/tools/master-ip-setup``, will be executed.
237

    
238
The ``-m (--mac-prefix)`` option will let you specify a three byte
239
prefix under which the virtual MAC addresses of your instances will be
240
generated. The prefix must be specified in the format ``XX:XX:XX`` and
241
the default is ``aa:00:00``.
242

    
243
The ``--no-lvm-storage`` option allows you to initialize the
244
cluster without lvm support. This means that only instances using
245
files as storage backend will be possible to create. Once the
246
cluster is initialized you can change this setup with the
247
**modify** command.
248

    
249
The ``--no-etc-hosts`` option allows you to initialize the cluster
250
without modifying the /etc/hosts file.
251

    
252
The ``--no-ssh-init`` option allows you to initialize the cluster
253
without creating or distributing SSH key pairs.
254

    
255
The ``--file-storage-dir`` option allows you set the directory to
256
use for storing the instance disk files when using file storage as
257
backend for instance disks.
258

    
259
The ``--prealloc-wipe-disks`` sets a cluster wide configuration
260
value for wiping disks prior to allocation. This increases security
261
on instance level as the instance can't access untouched data from
262
it's underlying storage.
263

    
264
The ``--enabled-hypervisors`` option allows you to set the list of
265
hypervisors that will be enabled for this cluster. Instance
266
hypervisors can only be chosen from the list of enabled
267
hypervisors, and the first entry of this list will be used by
268
default. Currently, the following hypervisors are available:
269

    
270
xen-pvm
271
    Xen PVM hypervisor
272

    
273
xen-hvm
274
    Xen HVM hypervisor
275

    
276
kvm
277
    Linux KVM hypervisor
278

    
279
chroot
280
    a simple chroot manager that starts chroot based on a script at the
281
    root of the filesystem holding the chroot
282

    
283
fake
284
    fake hypervisor for development/testing
285

    
286
Either a single hypervisor name or a comma-separated list of
287
hypervisor names can be specified. If this option is not specified,
288
only the xen-pvm hypervisor is enabled by default.
289

    
290
The ``-H (--hypervisor-parameters)`` option allows you to set default
291
hypervisor specific parameters for the cluster. The format of this
292
option is the name of the hypervisor, followed by a colon and a
293
comma-separated list of key=value pairs. The keys available for each
294
hypervisors are detailed in the gnt-instance(8) man page, in the
295
**add** command plus the following parameters which are only
296
configurable globally (at cluster level):
297

    
298
migration\_port
299
    Valid for the Xen PVM and KVM hypervisors.
300

    
301
    This options specifies the TCP port to use for live-migration. For
302
    Xen, the same port should be configured on all nodes in the
303
    ``/etc/xen/xend-config.sxp`` file, under the key
304
    "xend-relocation-port".
305

    
306
migration\_bandwidth
307
    Valid for the KVM hypervisor.
308

    
309
    This option specifies the maximum bandwidth that KVM will use for
310
    instance live migrations. The value is in MiB/s.
311

    
312
    This option is only effective with kvm versions >= 78 and qemu-kvm
313
    versions >= 0.10.0.
314

    
315
The ``-B (--backend-parameters)`` option allows you to set the default
316
backend parameters for the cluster. The parameter format is a
317
comma-separated list of key=value pairs with the following supported
318
keys:
319

    
320
vcpus
321
    Number of VCPUs to set for an instance by default, must be an
322
    integer, will be set to 1 if no specified.
323

    
324
maxmem
325
    Maximum amount of memory to allocate for an instance by default, can
326
    be either an integer or an integer followed by a unit (M for
327
    mebibytes and G for gibibytes are supported), will be set to 128M if
328
    not specified.
329

    
330
minmem
331
    Minimum amount of memory to allocate for an instance by default, can
332
    be either an integer or an integer followed by a unit (M for
333
    mebibytes and G for gibibytes are supported), will be set to 128M if
334
    not specified.
335

    
336
auto\_balance
337
    Value of the auto\_balance flag for instances to use by default,
338
    will be set to true if not specified.
339

    
340

    
341
The ``-N (--nic-parameters)`` option allows you to set the default nic
342
parameters for the cluster. The parameter format is a comma-separated
343
list of key=value pairs with the following supported keys:
344

    
345
mode
346
    The default nic mode, 'routed' or 'bridged'.
347

    
348
link
349
    In bridged mode the default NIC bridge. In routed mode it
350
    represents an hypervisor-vif-script dependent value to allow
351
    different instance groups. For example under the KVM default
352
    network script it is interpreted as a routing table number or
353
    name.
354

    
355
The option ``--maintain-node-health`` allows one to enable/disable
356
automatic maintenance actions on nodes. Currently these include
357
automatic shutdown of instances and deactivation of DRBD devices on
358
offline nodes; in the future it might be extended to automatic
359
removal of unknown LVM volumes, etc. Note that this option is only
360
useful if the use of ``ganeti-confd`` was enabled at compilation.
361

    
362
The ``--uid-pool`` option initializes the user-id pool. The
363
*user-id pool definition* can contain a list of user-ids and/or a
364
list of user-id ranges. The parameter format is a comma-separated
365
list of numeric user-ids or user-id ranges. The ranges are defined
366
by a lower and higher boundary, separated by a dash. The boundaries
367
are inclusive. If the ``--uid-pool`` option is not supplied, the
368
user-id pool is initialized to an empty list. An empty list means
369
that the user-id pool feature is disabled.
370

    
371
The ``-I (--default-iallocator)`` option specifies the default
372
instance allocator. The instance allocator will be used for operations
373
like instance creation, instance and node migration, etc. when no
374
manual override is specified. If this option is not specified and
375
htools was not enabled at build time, the default instance allocator
376
will be blank, which means that relevant operations will require the
377
administrator to manually specify either an instance allocator, or a
378
set of nodes. If the option is not specified but htools was enabled,
379
the default iallocator will be **hail**(1) (assuming it can be found
380
on disk). The default iallocator can be changed later using the
381
**modify** command.
382

    
383
The ``--primary-ip-version`` option specifies the IP version used
384
for the primary address. Possible values are 4 and 6 for IPv4 and
385
IPv6, respectively. This option is used when resolving node names
386
and the cluster name.
387

    
388
The ``--node-parameters`` option allows you to set default node
389
parameters for the cluster. Please see **ganeti**(7) for more
390
information about supported key=value pairs.
391

    
392
The ``-C (--candidate-pool-size)`` option specifies the
393
``candidate_pool_size`` cluster parameter. This is the number of nodes
394
that the master will try to keep as master\_candidates. For more
395
details about this role and other node roles, see the ganeti(7).
396

    
397
LIST-TAGS
398
~~~~~~~~~
399

    
400
**list-tags**
401

    
402
List the tags of the cluster.
403

    
404
MASTER-FAILOVER
405
~~~~~~~~~~~~~~~
406

    
407
**master-failover** [--no-voting]
408

    
409
Failover the master role to the current node.
410

    
411
The ``--no-voting`` option skips the remote node agreement checks.
412
This is dangerous, but necessary in some cases (for example failing
413
over the master role in a 2 node cluster with the original master
414
down). If the original master then comes up, it won't be able to
415
start its master daemon because it won't have enough votes, but so
416
won't the new master, if the master daemon ever needs a restart.
417
You can pass ``--no-voting`` to **ganeti-masterd** on the new
418
master to solve this problem, and run **gnt-cluster redist-conf**
419
to make sure the cluster is consistent again.
420

    
421
MASTER-PING
422
~~~~~~~~~~~
423

    
424
**master-ping**
425

    
426
Checks if the master daemon is alive.
427

    
428
If the master daemon is alive and can respond to a basic query (the
429
equivalent of **gnt-cluster info**), then the exit code of the
430
command will be 0. If the master daemon is not alive (either due to
431
a crash or because this is not the master node), the exit code will
432
be 1.
433

    
434
MODIFY
435
~~~~~~
436

    
437
| **modify**
438
| [--vg-name *vg-name*]
439
| [--no-lvm-storage]
440
| [--enabled-hypervisors *hypervisors*]
441
| [{-H|--hypervisor-parameters} *hypervisor*:*hv-param*=*value*[,*hv-param*=*value*...]]
442
| [{-B|--backend-parameters} *be-param*=*value* [,*be-param*=*value*...]]
443
| [{-N|--nic-parameters} *nic-param*=*value* [,*nic-param*=*value*...]]
444
| [--uid-pool *user-id pool definition*]
445
| [--add-uids *user-id pool definition*]
446
| [--remove-uids *user-id pool definition*]
447
| [{-C|--candidate-pool-size} *candidate\_pool\_size*]
448
| [--maintain-node-health {yes \| no}]
449
| [--prealloc-wipe-disks {yes \| no}]
450
| [{-I|--default-iallocator} *default instance allocator*]
451
| [--reserved-lvs=*NAMES*]
452
| [--node-parameters *ndparams*]
453
| [--master-netdev *interface-name*]
454
| [--master-netmask *netmask*]
455
| [--use-external-mip-script {yes \| no}]
456

    
457
Modify the options for the cluster.
458

    
459
The ``--vg-name``, ``--no-lvm-storarge``, ``--enabled-hypervisors``,
460
``-H (--hypervisor-parameters)``, ``-B (--backend-parameters)``,
461
``--nic-parameters``, ``-C (--candidate-pool-size)``,
462
``--maintain-node-health``, ``--prealloc-wipe-disks``, ``--uid-pool``,
463
``--node-parameters``, ``--master-netdev``, ``--master-netmask`` and
464
``--use-external-mip-script`` options are described in the
465
**init** command.
466

    
467
The ``--add-uids`` and ``--remove-uids`` options can be used to
468
modify the user-id pool by adding/removing a list of user-ids or
469
user-id ranges.
470

    
471
The option ``--reserved-lvs`` specifies a list (comma-separated) of
472
logical volume group names (regular expressions) that will be
473
ignored by the cluster verify operation. This is useful if the
474
volume group used for Ganeti is shared with the system for other
475
uses. Note that it's not recommended to create and mark as ignored
476
logical volume names which match Ganeti's own name format (starting
477
with UUID and then .diskN), as this option only skips the
478
verification, but not the actual use of the names given.
479

    
480
To remove all reserved logical volumes, pass in an empty argument
481
to the option, as in ``--reserved-lvs=`` or ``--reserved-lvs ''``.
482

    
483
The ``-I (--default-iallocator)`` is described in the **init**
484
command. To clear the default iallocator, just pass an empty string
485
('').
486

    
487
QUEUE
488
~~~~~
489

    
490
**queue** {drain | undrain | info}
491

    
492
Change job queue properties.
493

    
494
The ``drain`` option sets the drain flag on the job queue. No new
495
jobs will be accepted, but jobs already in the queue will be
496
processed.
497

    
498
The ``undrain`` will unset the drain flag on the job queue. New
499
jobs will be accepted.
500

    
501
The ``info`` option shows the properties of the job queue.
502

    
503
WATCHER
504
~~~~~~~
505

    
506
**watcher** {pause *duration* | continue | info}
507

    
508
Make the watcher pause or let it continue.
509

    
510
The ``pause`` option causes the watcher to pause for *duration*
511
seconds.
512

    
513
The ``continue`` option will let the watcher continue.
514

    
515
The ``info`` option shows whether the watcher is currently paused.
516

    
517
redist-conf
518
~~~~~~~~~~~
519

    
520
**redist-conf** [--submit]
521

    
522
This command forces a full push of configuration files from the
523
master node to the other nodes in the cluster. This is normally not
524
needed, but can be run if the **verify** complains about
525
configuration mismatches.
526

    
527
The ``--submit`` option is used to send the job to the master
528
daemon but not wait for its completion. The job ID will be shown so
529
that it can be examined via **gnt-job info**.
530

    
531
REMOVE-TAGS
532
~~~~~~~~~~~
533

    
534
**remove-tags** [--from *file*] {*tag*...}
535

    
536
Remove tags from the cluster. If any of the tags are not existing
537
on the cluster, the entire operation will abort.
538

    
539
If the ``--from`` option is given, the list of tags to be removed will
540
be extended with the contents of that file (each line becomes a tag).
541
In this case, there is not need to pass tags on the command line (if
542
you do, tags from both sources will be removed). A file name of - will
543
be interpreted as stdin.
544

    
545
RENAME
546
~~~~~~
547

    
548
**rename** [-f] {*name*}
549

    
550
Renames the cluster and in the process updates the master IP
551
address to the one the new name resolves to. At least one of either
552
the name or the IP address must be different, otherwise the
553
operation will be aborted.
554

    
555
Note that since this command can be dangerous (especially when run
556
over SSH), the command will require confirmation unless run with
557
the ``-f`` option.
558

    
559
RENEW-CRYPTO
560
~~~~~~~~~~~~
561

    
562
| **renew-crypto** [-f]
563
| [--new-cluster-certificate] [--new-confd-hmac-key]
564
| [--new-rapi-certificate] [--rapi-certificate *rapi-cert*]
565
| [--new-spice-certificate | --spice-certificate *spice-cert*
566
| -- spice-ca-certificate *spice-ca-cert*]
567
| [--new-cluster-domain-secret] [--cluster-domain-secret *filename*]
568

    
569
This command will stop all Ganeti daemons in the cluster and start
570
them again once the new certificates and keys are replicated. The
571
options ``--new-cluster-certificate`` and ``--new-confd-hmac-key``
572
can be used to regenerate the cluster-internal SSL certificate
573
respective the HMAC key used by ganeti-confd(8).
574

    
575
To generate a new self-signed RAPI certificate (used by
576
ganeti-rapi(8)) specify ``--new-rapi-certificate``. If you want to
577
use your own certificate, e.g. one signed by a certificate
578
authority (CA), pass its filename to ``--rapi-certificate``.
579

    
580
To generate a new self-signed SPICE certificate, used by SPICE
581
connections to the KVM hypervisor, specify the
582
``--new-spice-certificate`` option. If you want to provide a
583
certificate, pass its filename to ``--spice-certificate`` and pass the
584
signing CA certificate to ``--spice-ca-certificate``.
585

    
586
``--new-cluster-domain-secret`` generates a new, random cluster
587
domain secret. ``--cluster-domain-secret`` reads the secret from a
588
file. The cluster domain secret is used to sign information
589
exchanged between separate clusters via a third party.
590

    
591
REPAIR-DISK-SIZES
592
~~~~~~~~~~~~~~~~~
593

    
594
**repair-disk-sizes** [instance...]
595

    
596
This command checks that the recorded size of the given instance's
597
disks matches the actual size and updates any mismatches found.
598
This is needed if the Ganeti configuration is no longer consistent
599
with reality, as it will impact some disk operations. If no
600
arguments are given, all instances will be checked.
601

    
602
Note that only active disks can be checked by this command; in case
603
a disk cannot be activated it's advised to use
604
**gnt-instance activate-disks --ignore-size ...** to force
605
activation without regard to the current size.
606

    
607
When the all disk sizes are consistent, the command will return no
608
output. Otherwise it will log details about the inconsistencies in
609
the configuration.
610

    
611
SEARCH-TAGS
612
~~~~~~~~~~~
613

    
614
**search-tags** {*pattern*}
615

    
616
Searches the tags on all objects in the cluster (the cluster
617
itself, the nodes and the instances) for a given pattern. The
618
pattern is interpreted as a regular expression and a search will be
619
done on it (i.e. the given pattern is not anchored to the beggining
620
of the string; if you want that, prefix the pattern with ^).
621

    
622
If no tags are matching the pattern, the exit code of the command
623
will be one. If there is at least one match, the exit code will be
624
zero. Each match is listed on one line, the object and the tag
625
separated by a space. The cluster will be listed as /cluster, a
626
node will be listed as /nodes/*name*, and an instance as
627
/instances/*name*. Example:
628

    
629
::
630

    
631
    # gnt-cluster search-tags time
632
    /cluster ctime:2007-09-01
633
    /nodes/node1.example.com mtime:2007-10-04
634

    
635
VERIFY
636
~~~~~~
637

    
638
| **verify** [--no-nplus1-mem] [--node-group *nodegroup*]
639
| [--error-codes] [{-I|--ignore-errors} *errorcode*]
640
| [{-I|--ignore-errors} *errorcode*...]
641

    
642
Verify correctness of cluster configuration. This is safe with
643
respect to running instances, and incurs no downtime of the
644
instances.
645

    
646
If the ``--no-nplus1-mem`` option is given, Ganeti won't check
647
whether if it loses a node it can restart all the instances on
648
their secondaries (and report an error otherwise).
649

    
650
With ``--node-group``, restrict the verification to those nodes and
651
instances that live in the named group. This will not verify global
652
settings, but will allow to perform verification of a group while other
653
operations are ongoing in other groups.
654

    
655
The ``--error-codes`` option outputs each error in the following
656
parseable format: *ftype*:*ecode*:*edomain*:*name*:*msg*.
657
These fields have the following meaning:
658

    
659
ftype
660
    Failure type. Can be *WARNING* or *ERROR*.
661

    
662
ecode
663
    Error code of the failure. See below for a list of error codes.
664

    
665
edomain
666
    Can be *cluster*, *node* or *instance*.
667

    
668
name
669
    Contains the name of the item that is affected from the failure.
670

    
671
msg
672
    Contains a descriptive error message about the error
673

    
674
``gnt-cluster verify`` will have a non-zero exit code if at least one of
675
the failures that are found are of type *ERROR*.
676

    
677
The ``--ignore-errors`` option can be used to change this behaviour,
678
because it demotes the error represented by the error code received as a
679
parameter to a warning. The option must be repeated for each error that
680
should be ignored (e.g.: ``-I ENODEVERSION -I ENODEORPHANLV``). The
681
``--error-codes`` option can be used to determine the error code of a
682
given error.
683

    
684
List of error codes:
685

    
686
@CONSTANTS_ECODES@
687

    
688
VERIFY-DISKS
689
~~~~~~~~~~~~
690

    
691
**verify-disks**
692

    
693
The command checks which instances have degraded DRBD disks and
694
activates the disks of those instances.
695

    
696
This command is run from the **ganeti-watcher** tool, which also
697
has a different, complementary algorithm for doing this check.
698
Together, these two should ensure that DRBD disks are kept
699
consistent.
700

    
701
VERSION
702
~~~~~~~
703

    
704
**version**
705

    
706
Show the cluster version.
707

    
708
.. vim: set textwidth=72 :
709
.. Local Variables:
710
.. mode: rst
711
.. fill-column: 72
712
.. End: