Revision 354c4f62 man/gnt-cluster.rst
b/man/gnt-cluster.rst | ||
---|---|---|
33 | 33 |
**command** [-n *node*] [-g *group*] [-M] {*command*} |
34 | 34 |
|
35 | 35 |
Executes a command on all nodes. This command is designed for simple |
36 |
usage. For more complex use cases the commands **dsh(1)** or **cssh(1)**
|
|
36 |
usage. For more complex use cases the commands **dsh**\(1) or **cssh**\(1)
|
|
37 | 37 |
should be used instead. |
38 | 38 |
|
39 | 39 |
If the option ``-n`` is not given, the command will be executed on all |
... | ... | |
293 | 293 |
hypervisor specific parameters for the cluster. The format of this |
294 | 294 |
option is the name of the hypervisor, followed by a colon and a |
295 | 295 |
comma-separated list of key=value pairs. The keys available for each |
296 |
hypervisors are detailed in the gnt-instance(8) man page, in the
|
|
296 |
hypervisors are detailed in the **gnt-instance**\(8) man page, in the
|
|
297 | 297 |
**add** command plus the following parameters which are only |
298 | 298 |
configurable globally (at cluster level): |
299 | 299 |
|
... | ... | |
369 | 369 |
list of key-value pairs. These parameters can only be specified at |
370 | 370 |
cluster and node group level; the cluster-level parameter are inherited |
371 | 371 |
by the node group at the moment of its creation, and can be further |
372 |
modified at node group level using the **gnt-group**(8) command. |
|
372 |
modified at node group level using the **gnt-group**\(8) command.
|
|
373 | 373 |
|
374 | 374 |
The following is the list of disk parameters available for the **drbd** |
375 | 375 |
template, with measurement units specified in square brackets at the end |
... | ... | |
470 | 470 |
will be blank, which means that relevant operations will require the |
471 | 471 |
administrator to manually specify either an instance allocator, or a |
472 | 472 |
set of nodes. If the option is not specified but htools was enabled, |
473 |
the default iallocator will be **hail**(1) (assuming it can be found |
|
473 |
the default iallocator will be **hail**\(1) (assuming it can be found
|
|
474 | 474 |
on disk). The default iallocator can be changed later using the |
475 | 475 |
**modify** command. |
476 | 476 |
|
... | ... | |
480 | 480 |
and the cluster name. |
481 | 481 |
|
482 | 482 |
The ``--node-parameters`` option allows you to set default node |
483 |
parameters for the cluster. Please see **ganeti**(7) for more |
|
483 |
parameters for the cluster. Please see **ganeti**\(7) for more
|
|
484 | 484 |
information about supported key=value pairs. |
485 | 485 |
|
486 | 486 |
The ``-C (--candidate-pool-size)`` option specifies the |
487 | 487 |
``candidate_pool_size`` cluster parameter. This is the number of nodes |
488 | 488 |
that the master will try to keep as master\_candidates. For more |
489 |
details about this role and other node roles, see the ganeti(7).
|
|
489 |
details about this role and other node roles, see the **ganeti**\(7).
|
|
490 | 490 |
|
491 | 491 |
The ``--specs-...`` and ``--ipolicy-disk-templates`` options specify |
492 | 492 |
instance policy on the cluster. For the ``--specs-...`` options, each |
... | ... | |
506 | 506 |
- ``--ipolicy-disk-templates`` limits the allowed disk templates |
507 | 507 |
|
508 | 508 |
For details about how to use ``--hypervisor-state`` and ``--disk-state`` |
509 |
have a look at **ganeti**(7). |
|
509 |
have a look at **ganeti**\(7).
|
|
510 | 510 |
|
511 | 511 |
MASTER-FAILOVER |
512 | 512 |
~~~~~~~~~~~~~~~ |
... | ... | |
588 | 588 |
command. |
589 | 589 |
|
590 | 590 |
The ``--hypervisor-state`` and ``--disk-state`` options are described in |
591 |
detail in **ganeti(7)**.
|
|
591 |
detail in **ganeti**\(7).
|
|
592 | 592 |
|
593 | 593 |
The ``--add-uids`` and ``--remove-uids`` options can be used to |
594 | 594 |
modify the user-id pool by adding/removing a list of user-ids or |
... | ... | |
613 | 613 |
The ``--specs-...`` and ``--ipolicy-disk-templates`` options are |
614 | 614 |
described in the **init** command. |
615 | 615 |
|
616 |
See **ganeti(7)** for a description of ``--submit`` and other common
|
|
616 |
See **ganeti**\(7) for a description of ``--submit`` and other common
|
|
617 | 617 |
options. |
618 | 618 |
|
619 | 619 |
QUEUE |
... | ... | |
656 | 656 |
needed, but can be run if the **verify** complains about |
657 | 657 |
configuration mismatches. |
658 | 658 |
|
659 |
See **ganeti(7)** for a description of ``--submit`` and other common
|
|
659 |
See **ganeti**\(7) for a description of ``--submit`` and other common
|
|
660 | 660 |
options. |
661 | 661 |
|
662 | 662 |
RENAME |
... | ... | |
687 | 687 |
them again once the new certificates and keys are replicated. The |
688 | 688 |
options ``--new-cluster-certificate`` and ``--new-confd-hmac-key`` |
689 | 689 |
can be used to regenerate the cluster-internal SSL certificate |
690 |
respective the HMAC key used by ganeti-confd(8).
|
|
690 |
respective the HMAC key used by **ganeti-confd**\(8).
|
|
691 | 691 |
|
692 | 692 |
To generate a new self-signed RAPI certificate (used by |
693 |
ganeti-rapi(8)) specify ``--new-rapi-certificate``. If you want to
|
|
693 |
**ganeti-rapi**\(8)) specify ``--new-rapi-certificate``. If you want to
|
|
694 | 694 |
use your own certificate, e.g. one signed by a certificate |
695 | 695 |
authority (CA), pass its filename to ``--rapi-certificate``. |
696 | 696 |
|
Also available in: Unified diff