Add new back-end parameter "always_failover"

[ganeti-local] / man / gnt-node.rst

diff --git a/man/gnt-node.rst b/man/gnt-node.rst
index 71995c5..e2ddae6 100644 (file)
--- a/man/gnt-node.rst
+++ b/man/gnt-node.rst
@@ -115,6 +115,14 @@ old storage is already broken) or when the storage on the primary
 node is known to be fine (thus we won't need the old storage for
 potential recovery).
 
+Note that this command is equivalent to using per-instance commands for
+each affected instance individually:
+
+- ``--primary-only`` is equivalent to ``gnt-instance failover/migration``
+- ``--secondary-only`` is equivalent to ``gnt-instance replace-disks``
+  in the secondary node change mode (only valid for DRBD instances)
+- when neither of the above is done a combination of the two cases is run
+
 Example::
 
     # gnt-node evacuate -I hail node3.example.com
@@ -253,6 +261,8 @@ MODIFY
 | [{-s|--secondary-ip} *secondary_ip*]
 | [--node-parameters *ndparams*]
 | [--node-powered=``yes|no``]
+| [--hypervisor-state *hvstate*]
+| [--disk-state *diskstate*]
 | {*node*}
 
 This command changes the role of the node. Each options takes
@@ -482,7 +492,7 @@ POWERCYCLE
 
 **powercycle** [``--yes``] [``--force``] {*node*}
 
-This commands (tries to) forcefully reboot a node. It is a command
+This command (tries to) forcefully reboot a node. It is a command
 that can be used if the node environemnt is broken, such that the
 admin can no longer login over ssh, but the Ganeti node daemon is
 still working.
@@ -502,7 +512,7 @@ POWER
 **power** [``--force``] [``--ignore-status``] [``--all``]
 [``--power-delay``] on|off|cycle|status [*nodes*]
 
-This commands calls out to out-of-band management to change the power
+This command calls out to out-of-band management to change the power
 state of given node. With ``status`` you get the power status as reported
 by the out-of-band managment script.
 
@@ -533,7 +543,7 @@ HEALTH
 
 **health** [*nodes*]
 
-This commands calls out to out-pf-band management to ask for the health status
+This command calls out to out-of-band management to ask for the health status
 of all or given nodes. The health contains the node name and then the items
 element with their status in a ``item=status`` manner. Where ``item`` is script
 specific and ``status`` can be one of ``OK``, ``WARNING``, ``CRITICAL`` or