X-Git-Url: https://code.grnet.gr/git/ganeti-local/blobdiff_plain/745dae57563d2f102ec8cd30349d663336309692..dbc6f6dd180727236bedbadaf5d97dd17076ba4e:/man/gnt-cluster.rst diff --git a/man/gnt-cluster.rst b/man/gnt-cluster.rst index d543682..8bfff33 100644 --- a/man/gnt-cluster.rst +++ b/man/gnt-cluster.rst @@ -27,29 +27,18 @@ ACTIVATE-MASTER-IP Activates the master IP on the master node. -ADD-TAGS -~~~~~~~~ - -**add-tags** [\--from *file*] {*tag*...} - -Add tags to the cluster. If any of the tags contains invalid -characters, the entire operation will abort. - -If the ``--from`` option is given, the list of tags will be -extended with the contents of that file (each line becomes a tag). -In this case, there is not need to pass tags on the command line -(if you do, both sources will be used). A file name of - will be -interpreted as stdin. - COMMAND ~~~~~~~ **command** [-n *node*] [-g *group*] [-M] {*command*} -Executes a command on all nodes. If the option ``-n`` is not given, -the command will be executed on all nodes, otherwise it will be -executed only on the node(s) specified. Use the option multiple -times for running it on multiple nodes, like:: +Executes a command on all nodes. This command is designed for simple +usage. For more complex use cases the commands **dsh**\(1) or **cssh**\(1) +should be used instead. + +If the option ``-n`` is not given, the command will be executed on all +nodes, otherwise it will be executed only on the node(s) specified. Use +the option multiple times for running it on multiple nodes, like:: # gnt-cluster command -n node1.example.com -n node2.example.com date @@ -59,7 +48,8 @@ group, e.g.:: # gnt-cluster command -g default date The ``-M`` option can be used to prepend the node name to all output -lines. +lines. The ``--failure-only`` option hides successful commands, making +it easier to see failures. The command is executed serially on the selected nodes. If the master node is present in the list, the command will be executed @@ -172,7 +162,6 @@ INIT | [\--master-netmask *netmask*] | [\--use-external-mip-script {yes \| no}] | [{-m|\--mac-prefix} *mac-prefix*] -| [\--no-lvm-storage] | [\--no-etc-hosts] | [\--no-ssh-init] | [\--file-storage-dir *dir*] @@ -193,9 +182,10 @@ INIT | [\--specs-disk-size *spec-param*=*value* [,*spec-param*=*value*...]] | [\--specs-mem-size *spec-param*=*value* [,*spec-param*=*value*...]] | [\--specs-nic-count *spec-param*=*value* [,*spec-param*=*value*...]] -| [\--ipol-disk-templates *template* [,*template*...]] +| [\--ipolicy-disk-templates *template* [,*template*...]] | [\--disk-state *diskstate*] | [\--hypervisor-state *hvstate*] +| [\--enabled-disk-templates *template* [,*template*...]] | {*clustername*} This commands is only run once initially on the first node of the @@ -228,7 +218,8 @@ different than "xenvg" for Ganeti to use when creating instance disks. This volume group must have the same name on all nodes. Once the cluster is initialized this can be altered by using the **modify** command. If you don't want to use lvm storage at all use -the ``--no-lvm-storage`` option. Once the cluster is initialized +the ``--enabled-disk-template`` option to restrict the set of enabled +disk templates. Once the cluster is initialized you can change this setup with the **modify** command. The ``--master-netdev`` option is useful for specifying a different @@ -241,23 +232,17 @@ master IP. The netmask must be specified as an integer, and will be interpreted as a CIDR netmask. The default value is 32 for an IPv4 address and 128 for an IPv6 address. -The ``--use-external-mip-script`` options allows to specify -whether to use an user-supplied master IP address setup script, whose -location is ``/etc/ganeti/scripts/master-ip-setup``. If the option value -is set to False, the default script, whose location is -``/usr/local/lib/ganeti/tools/master-ip-setup``, will be executed. +The ``--use-external-mip-script`` option allows to specify whether to +use an user-supplied master IP address setup script, whose location is +``@SYSCONFDIR@/ganeti/scripts/master-ip-setup``. If the option value is +set to False, the default script (located at +``@PKGLIBDIR@/tools/master-ip-setup``) will be executed. The ``-m (--mac-prefix)`` option will let you specify a three byte prefix under which the virtual MAC addresses of your instances will be generated. The prefix must be specified in the format ``XX:XX:XX`` and the default is ``aa:00:00``. -The ``--no-lvm-storage`` option allows you to initialize the -cluster without lvm support. This means that only instances using -files as storage backend will be possible to create. Once the -cluster is initialized you can change this setup with the -**modify** command. - The ``--no-etc-hosts`` option allows you to initialize the cluster without modifying the /etc/hosts file. @@ -268,10 +253,10 @@ The ``--file-storage-dir`` option allows you set the directory to use for storing the instance disk files when using file storage as backend for instance disks. -The ``--prealloc-wipe-disks`` sets a cluster wide configuration -value for wiping disks prior to allocation. This increases security -on instance level as the instance can't access untouched data from -it's underlying storage. +The ``--prealloc-wipe-disks`` sets a cluster wide configuration value +for wiping disks prior to allocation and size changes (``gnt-instance +grow-disk``). This increases security on instance level as the instance +can't access untouched data from its underlying storage. The ``--enabled-hypervisors`` option allows you to set the list of hypervisors that will be enabled for this cluster. Instance @@ -303,7 +288,7 @@ The ``-H (--hypervisor-parameters)`` option allows you to set default hypervisor specific parameters for the cluster. The format of this option is the name of the hypervisor, followed by a colon and a comma-separated list of key=value pairs. The keys available for each -hypervisors are detailed in the gnt-instance(8) man page, in the +hypervisors are detailed in the **gnt-instance**\(8) man page, in the **add** command plus the following parameters which are only configurable globally (at cluster level): @@ -312,7 +297,7 @@ migration\_port This options specifies the TCP port to use for live-migration. For Xen, the same port should be configured on all nodes in the - ``/etc/xen/xend-config.sxp`` file, under the key + ``@XEN_CONFIG_DIR@/xend-config.sxp`` file, under the key "xend-relocation-port". migration\_bandwidth @@ -350,23 +335,27 @@ auto\_balance will be set to true if not specified. always\_failover - Default value for the ``always\_failover`` flag for instances; if + Default value for the ``always_failover`` flag for instances; if not set, ``False`` is used. -The ``-N (--nic-parameters)`` option allows you to set the default nic -parameters for the cluster. The parameter format is a comma-separated -list of key=value pairs with the following supported keys: +The ``-N (--nic-parameters)`` option allows you to set the default +network interface parameters for the cluster. The parameter format is a +comma-separated list of key=value pairs with the following supported +keys: mode - The default nic mode, 'routed' or 'bridged'. + The default NIC mode, one of ``routed``, ``bridged`` or + ``openvswitch``. link - In bridged mode the default NIC bridge. In routed mode it - represents an hypervisor-vif-script dependent value to allow - different instance groups. For example under the KVM default - network script it is interpreted as a routing table number or - name. + In ``bridged`` or ``openvswitch`` mode the default interface where + to attach NICs. In ``routed`` mode it represents an + hypervisor-vif-script dependent value to allow different instance + groups. For example under the KVM default network script it is + interpreted as a routing table number or name. Openvswitch support + is also hypervisor dependent and currently works for the default KVM + network script. Under Xen a custom network script must be provided. The ``-D (--disk-parameters)`` option allows you to set the default disk template parameters at cluster level. The format used for this option is @@ -375,7 +364,7 @@ must be specified first, followed by a colon and by a comma-separated list of key-value pairs. These parameters can only be specified at cluster and node group level; the cluster-level parameter are inherited by the node group at the moment of its creation, and can be further -modified at node group level using the **gnt-group**(8) command. +modified at node group level using the **gnt-group**\(8) command. The following is the list of disk parameters available for the **drbd** template, with measurement units specified in square brackets at the end @@ -476,7 +465,7 @@ htools was not enabled at build time, the default instance allocator will be blank, which means that relevant operations will require the administrator to manually specify either an instance allocator, or a set of nodes. If the option is not specified but htools was enabled, -the default iallocator will be **hail**(1) (assuming it can be found +the default iallocator will be **hail**\(1) (assuming it can be found on disk). The default iallocator can be changed later using the **modify** command. @@ -486,21 +475,21 @@ IPv6, respectively. This option is used when resolving node names and the cluster name. The ``--node-parameters`` option allows you to set default node -parameters for the cluster. Please see **ganeti**(7) for more +parameters for the cluster. Please see **ganeti**\(7) for more information about supported key=value pairs. The ``-C (--candidate-pool-size)`` option specifies the ``candidate_pool_size`` cluster parameter. This is the number of nodes that the master will try to keep as master\_candidates. For more -details about this role and other node roles, see the ganeti(7). +details about this role and other node roles, see the **ganeti**\(7). -The ``--specs-...`` and ``--ipol-disk-templates`` options specify +The ``--specs-...`` and ``--ipolicy-disk-templates`` options specify instance policy on the cluster. For the ``--specs-...`` options, each option can have three values: ``min``, ``max`` and ``std``, which can also be modified on group level (except for ``std``, which is defined once for the entire cluster). Please note, that ``std`` values are not the same as defaults set by ``--beparams``, but they are used for the -capacity calculations. The ``--ipol-disk-templates`` option takes a +capacity calculations. The ``--ipolicy-disk-templates`` option takes a comma-separated list of disk templates. - ``--specs-cpu-count`` limits the number of VCPUs that can be used by an @@ -509,22 +498,23 @@ comma-separated list of disk templates. - ``--specs-disk-size`` limits the disk size for every disk used - ``--specs-mem-size`` limits the amount of memory available - ``--specs-nic-count`` sets limits on the number of NICs used -- ``--ipol-disk-templates`` limits the allowed disk templates +- ``--ipolicy-disk-templates`` limits the allowed disk templates For details about how to use ``--hypervisor-state`` and ``--disk-state`` -have a look at **ganeti**(7). - -LIST-TAGS -~~~~~~~~~ +have a look at **ganeti**\(7). -**list-tags** - -List the tags of the cluster. +The ``--enabled-disk-templates`` option specifies a list of disk templates +that can be used by instances of the cluster. For the possible values in +this list, see **gnt-instance**\(8). Note that in contrast to the list of +disk templates in the ipolicy, this list is a hard restriction. It is not +possible to create instances with disk templates that are not enabled in +the cluster. It is also not possible to disable a disk template when there +are still instances using it. MASTER-FAILOVER ~~~~~~~~~~~~~~~ -**master-failover** [\--no-voting] +**master-failover** [\--no-voting] [\--yes-do-it] Failover the master role to the current node. @@ -538,6 +528,11 @@ You can pass ``--no-voting`` to **ganeti-masterd** on the new master to solve this problem, and run **gnt-cluster redist-conf** to make sure the cluster is consistent again. +The option ``--yes-do-it`` is used together with ``--no-voting``, for +skipping the interactive checks. This is even more dangerous, and should +only be used in conjunction with other means (e.g. a HA suite) to +confirm that the operation is indeed safe. + MASTER-PING ~~~~~~~~~~~ @@ -556,7 +551,6 @@ MODIFY | **modify** [\--submit] | [\--vg-name *vg-name*] -| [\--no-lvm-storage] | [\--enabled-hypervisors *hypervisors*] | [{-H|\--hypervisor-parameters} *hypervisor*:*hv-param*=*value*[,*hv-param*=*value*...]] | [{-B|\--backend-parameters} *be-param*=*value*[,*be-param*=*value*...]] @@ -581,22 +575,22 @@ MODIFY | [\--specs-disk-size *spec-param*=*value* [,*spec-param*=*value*...]] | [\--specs-mem-size *spec-param*=*value* [,*spec-param*=*value*...]] | [\--specs-nic-count *spec-param*=*value* [,*spec-param*=*value*...]] -| [\--ipol-disk-templates *template* [,*template*...]] +| [\--ipolicy-disk-templates *template* [,*template*...]] +| [\--enabled-disk-templates *template* [,*template*...]] Modify the options for the cluster. -The ``--vg-name``, ``--no-lvm-storarge``, ``--enabled-hypervisors``, -``-H (--hypervisor-parameters)``, ``-B (--backend-parameters)``, -``-D (--disk-parameters)``, ``--nic-parameters``, ``-C -(--candidate-pool-size)``, ``--maintain-node-health``, +The ``--vg-name``, ``--enabled-hypervisors``, ``-H (--hypervisor-parameters)``, +``-B (--backend-parameters)``, ``-D (--disk-parameters)``, ``--nic-parameters``, +``-C (--candidate-pool-size)``, ``--maintain-node-health``, ``--prealloc-wipe-disks``, ``--uid-pool``, ``--node-parameters``, -``--master-netdev``, ``--master-netmask`` and -``--use-external-mip-script`` options are described in the **init** +``--master-netdev``, ``--master-netmask``, ``--use-external-mip-script``, +and ``--enabled-disk-templates`` options are described in the **init** command. The ``--hypervisor-state`` and ``--disk-state`` options are described in -detail in **ganeti(7)**. +detail in **ganeti**\(7). The ``--add-uids`` and ``--remove-uids`` options can be used to modify the user-id pool by adding/removing a list of user-ids or @@ -618,10 +612,10 @@ The ``-I (--default-iallocator)`` is described in the **init** command. To clear the default iallocator, just pass an empty string (''). -The ``--specs-...`` and ``--ipol-disk-templates`` options are described -in the **init** command. +The ``--specs-...`` and ``--ipolicy-disk-templates`` options are +described in the **init** command. -See **ganeti(7)** for a description of ``--submit`` and other common +See **ganeti**\(7) for a description of ``--submit`` and other common options. QUEUE @@ -654,7 +648,7 @@ The ``continue`` option will let the watcher continue. The ``info`` option shows whether the watcher is currently paused. -redist-conf +REDIST-CONF ~~~~~~~~~~~ **redist-conf** [\--submit] @@ -664,23 +658,9 @@ master node to the other nodes in the cluster. This is normally not needed, but can be run if the **verify** complains about configuration mismatches. -See **ganeti(7)** for a description of ``--submit`` and other common +See **ganeti**\(7) for a description of ``--submit`` and other common options. -REMOVE-TAGS -~~~~~~~~~~~ - -**remove-tags** [\--from *file*] {*tag*...} - -Remove tags from the cluster. If any of the tags are not existing -on the cluster, the entire operation will abort. - -If the ``--from`` option is given, the list of tags to be removed will -be extended with the contents of that file (each line becomes a tag). -In this case, there is not need to pass tags on the command line (if -you do, tags from both sources will be removed). A file name of - will -be interpreted as stdin. - RENAME ~~~~~~ @@ -709,10 +689,10 @@ This command will stop all Ganeti daemons in the cluster and start them again once the new certificates and keys are replicated. The options ``--new-cluster-certificate`` and ``--new-confd-hmac-key`` can be used to regenerate the cluster-internal SSL certificate -respective the HMAC key used by ganeti-confd(8). +respective the HMAC key used by **ganeti-confd**\(8). To generate a new self-signed RAPI certificate (used by -ganeti-rapi(8)) specify ``--new-rapi-certificate``. If you want to +**ganeti-rapi**\(8)) specify ``--new-rapi-certificate``. If you want to use your own certificate, e.g. one signed by a certificate authority (CA), pass its filename to ``--rapi-certificate``. @@ -747,30 +727,6 @@ When the all disk sizes are consistent, the command will return no output. Otherwise it will log details about the inconsistencies in the configuration. -SEARCH-TAGS -~~~~~~~~~~~ - -**search-tags** {*pattern*} - -Searches the tags on all objects in the cluster (the cluster -itself, the nodes and the instances) for a given pattern. The -pattern is interpreted as a regular expression and a search will be -done on it (i.e. the given pattern is not anchored to the beggining -of the string; if you want that, prefix the pattern with ^). - -If no tags are matching the pattern, the exit code of the command -will be one. If there is at least one match, the exit code will be -zero. Each match is listed on one line, the object and the tag -separated by a space. The cluster will be listed as /cluster, a -node will be listed as /nodes/*name*, and an instance as -/instances/*name*. Example: - -:: - - # gnt-cluster search-tags time - /cluster ctime:2007-09-01 - /nodes/node1.example.com mtime:2007-10-04 - VERIFY ~~~~~~ @@ -844,6 +800,68 @@ VERSION Show the cluster version. +Tags +~~~~ + +ADD-TAGS +^^^^^^^^ + +**add-tags** [\--from *file*] {*tag*...} + +Add tags to the cluster. If any of the tags contains invalid +characters, the entire operation will abort. + +If the ``--from`` option is given, the list of tags will be +extended with the contents of that file (each line becomes a tag). +In this case, there is not need to pass tags on the command line +(if you do, both sources will be used). A file name of - will be +interpreted as stdin. + +LIST-TAGS +^^^^^^^^^ + +**list-tags** + +List the tags of the cluster. + +REMOVE-TAGS +^^^^^^^^^^^ + +**remove-tags** [\--from *file*] {*tag*...} + +Remove tags from the cluster. If any of the tags are not existing +on the cluster, the entire operation will abort. + +If the ``--from`` option is given, the list of tags to be removed will +be extended with the contents of that file (each line becomes a tag). +In this case, there is not need to pass tags on the command line (if +you do, tags from both sources will be removed). A file name of - will +be interpreted as stdin. + +SEARCH-TAGS +^^^^^^^^^^^ + +**search-tags** {*pattern*} + +Searches the tags on all objects in the cluster (the cluster +itself, the nodes and the instances) for a given pattern. The +pattern is interpreted as a regular expression and a search will be +done on it (i.e. the given pattern is not anchored to the beggining +of the string; if you want that, prefix the pattern with ^). + +If no tags are matching the pattern, the exit code of the command +will be one. If there is at least one match, the exit code will be +zero. Each match is listed on one line, the object and the tag +separated by a space. The cluster will be listed as /cluster, a +node will be listed as /nodes/*name*, and an instance as +/instances/*name*. Example: + +:: + + # gnt-cluster search-tags time + /cluster ctime:2007-09-01 + /nodes/node1.example.com mtime:2007-10-04 + .. vim: set textwidth=72 : .. Local Variables: .. mode: rst