Revision 50c1e351 man/gnt-node.rst

b/man/gnt-node.rst
220 220
other fields are "live" fields and require a query to the cluster nodes.
221 221

  
222 222
Depending on the virtualization type and implementation details, the
223
``mtotal``, ``mnode`` and ``mfree`` fields may have slighly varying
223
``mtotal``, ``mnode`` and ``mfree`` fields may have slightly varying
224 224
meanings. For example, some solutions share the node memory with the
225 225
pool of memory used for instances (KVM), whereas others have separate
226 226
memory for the node and for the instances (Xen).
......
295 295
``--no-live``, ``--migration-mode`` and ``--no-runtime-changes``
296 296
can be given to influence the migration type.
297 297

  
298
If ``--ignore-ipolicy`` is given any instance policy violations occuring
299
during this operation are ignored.
298
If ``--ignore-ipolicy`` is given any instance policy violations
299
occurring during this operation are ignored.
300 300

  
301 301
See **ganeti(7)** for a description of ``--submit`` and other common
302 302
options.
......
575 575

  
576 576
This command calls out to out-of-band management to change the power
577 577
state of given node. With ``status`` you get the power status as reported
578
by the out-of-band managment script.
578
by the out-of-band management script.
579 579

  
580 580
Note that this command will only work if the out-of-band functionality
581 581
is configured and enabled on the cluster. If this is not the case,

Also available in: Unified diff