In Ganeti 2.0, the architecture of the cluster is a little more
complicated than in 1.2. The cluster is coordinated by a master daemon
-(**ganeti-masterd**(8)), running on the master node. Each node runs
+(**ganeti-masterd**\(8)), running on the master node. Each node runs
(as before) a node daemon, and the master has the RAPI daemon running
too.
hard-drives, its meaning is site-local and just the relative values
matter.
+exclusive_storage
+ When this Boolean flag is enabled, physical disks on the node are
+ assigned to instance disks in an exclusive manner, so as to lower I/O
+ interference between instances. See the `Partitioned Ganeti
+ <design-partitioned.rst>`_ design document for more details. This
+ parameter cannot be set on individual nodes, as its value must be
+ the same within each node group.
+
Hypervisor State Parameters
~~~~~~~~~~~~~~~~~~~~~~~~~~~
discovered or set manually. Only used for estimating how many VCPUs
are left for instances
+Note that currently this option is unused by Ganeti; values will be
+recorded but will not influence the Ganeti operation.
+
Disk State Parameters
~~~~~~~~~~~~~~~~~~~~~
Disk that is expected to be used by other volumes (set via
``reserved_lvs``); usually should be zero
+Note that currently this option is unused by Ganeti; values will be
+recorded but will not influence the Ganeti operation.
+
Cluster configuration
~~~~~~~~~~~~~~~~~~~~~
availability for a certain command can be checked by calling the
command using the ``--help`` option.
-**gnt-...** *command* [\--dry-run] [\--priority {low | normal | high}]
+| **gnt-...** *command* [\--dry-run] [\--priority {low | normal | high}]
+| [\--submit]
The ``--dry-run`` option can be used to check whether an operation
would succeed.
The option ``--priority`` sets the priority for opcodes submitted
by the command.
+The ``--submit`` option is used to send the job to the master daemon but
+not wait for its completion. The job ID will be shown so that it can be
+examined using **gnt-job info**.
+
Defaults
~~~~~~~~
flags by setting ``GNT_NODE_LIST``, ``GNT_GROUP_LIST`` and
``GNT_INSTANCE_LIST``.
+Debug options
+~~~~~~~~~~~~~
+
+If the variable ``FORCE_LUXI_SOCKET`` is set, it will override the
+socket used for LUXI connections by command-line tools
+(``gnt-*``). This is useful mostly for debugging, and some operations
+won't work at all if, for example, you point this variable to the
+confd-supplied query socket and try to submit a job.
+
+If the variable is set to the value ``master``, it will connect to the
+correct path for the master daemon (even if, for example, split
+queries are enabled and this is a query operation). If set to
+``query``, it will always (try to) connect to the query socket, even
+if split queries are disabled. Otherwise, the value is taken to
+represent a filesystem path to the socket to use.
+
Field formatting
----------------
<condition> ::=
{ /* Value comparison */
- <field> { == | != } <value>
+ <field> { == | != | < | <= | >= | > } <value>
/* Collection membership */
| <value> [ not ] in <field>
Equality
*!=*
Inequality
+*<*
+ Less than
+*<=*
+ Less than or equal
+*>*
+ Greater than
+*>=*
+ Greater than or equal
*=~*
Pattern match using regular expression
*!~*
Logically negated from *=~*
*=\**
- Globbing, see **glob**(7), though only * and ? are supported
+ Globbing, see **glob**\(7), though only * and ? are supported
*!\**
Logically negated from *=\**
*in*, *not in*
---------------------------
All Ganeti daemons re-open the log file(s) when sent a SIGHUP signal.
-**logrotate**(8) can be used to rotate Ganeti's log files.
+**logrotate**\(8) can be used to rotate Ganeti's log files.
.. vim: set textwidth=72 :
.. Local Variables: