Revision 22ac4136
| b/NEWS | ||
|---|---|---|
| 703 | 703 |
- Instance migration can fall back to failover if instance is not |
| 704 | 704 |
running. |
| 705 | 705 |
- Filters can be used when listing nodes, instances, groups and locks; |
| 706 |
see *ganeti(7)* manpage.
|
|
| 706 |
see :manpage:`ganeti(7)` manpage.
|
|
| 707 | 707 |
- Added post-execution status as variables to :doc:`hooks <hooks>` |
| 708 | 708 |
environment. |
| 709 | 709 |
- Instance tags are exported/imported together with the instance. |
| b/doc/admin.rst | ||
|---|---|---|
| 322 | 322 |
.. warning:: Do not use the Xen or KVM commands directly to stop |
| 323 | 323 |
instances. If you run for example ``xm shutdown`` or ``xm destroy`` |
| 324 | 324 |
on an instance Ganeti will automatically restart it (via |
| 325 |
the :command:`ganeti-watcher` command which is launched via cron). |
|
| 325 |
the :command:`ganeti-watcher(8)` command which is launched via cron).
|
|
| 326 | 326 |
|
| 327 | 327 |
Querying instances |
| 328 | 328 |
~~~~~~~~~~~~~~~~~~ |
| ... | ... | |
| 1217 | 1217 |
Watcher control |
| 1218 | 1218 |
+++++++++++++++ |
| 1219 | 1219 |
|
| 1220 |
The :manpage:`ganeti-watcher` is a program, usually scheduled via |
|
| 1220 |
The :manpage:`ganeti-watcher(8)` is a program, usually scheduled via
|
|
| 1221 | 1221 |
``cron``, that takes care of cluster maintenance operations (restarting |
| 1222 | 1222 |
downed instances, activating down DRBD disks, etc.). However, during |
| 1223 | 1223 |
maintenance and troubleshooting, this can get in your way; disabling it |
| b/doc/design-2.0.rst | ||
|---|---|---|
| 1621 | 1621 |
|
| 1622 | 1622 |
These are only the basic variables we are thinking of now, but more |
| 1623 | 1623 |
may come during the implementation and they will be documented in the |
| 1624 |
:manpage:`ganeti-os-api` man page. All these variables will be
|
|
| 1624 |
:manpage:`ganeti-os-interface(7)` man page. All these variables will be
|
|
| 1625 | 1625 |
available to all scripts. |
| 1626 | 1626 |
|
| 1627 | 1627 |
Some scripts will need a few more information to work. These will have |
| b/doc/install.rst | ||
|---|---|---|
| 655 | 655 |
can be added, of course, if needed. |
| 656 | 656 |
|
| 657 | 657 |
Alternatively, you can create your own OS definitions. See the manpage |
| 658 |
:manpage:`ganeti-os-interface`. |
|
| 658 |
:manpage:`ganeti-os-interface(7)`.
|
|
| 659 | 659 |
|
| 660 | 660 |
Initializing the cluster |
| 661 | 661 |
++++++++++++++++++++++++ |
| b/man/gnt-backup.rst | ||
|---|---|---|
| 30 | 30 |
|
| 31 | 31 |
Exports an instance to the target node. All the instance data and |
| 32 | 32 |
its configuration will be exported under the |
| 33 |
``@CUSTOM_EXPORT_DIR@/``*instance* directory on the target node.
|
|
| 33 |
``@CUSTOM_EXPORT_DIR@/$instance`` directory on the target node.
|
|
| 34 | 34 |
|
| 35 | 35 |
The ``--shutdown-timeout`` is used to specify how much time to wait |
| 36 | 36 |
before forcing the shutdown (xm destroy in xen, killing the kvm |
| b/man/gnt-cluster.rst | ||
|---|---|---|
| 340 | 340 |
will be set to true if not specified. |
| 341 | 341 |
|
| 342 | 342 |
always\_failover |
| 343 |
Default value for the ``always\_failover`` flag for instances; if
|
|
| 343 |
Default value for the ``always_failover`` flag for instances; if |
|
| 344 | 344 |
not set, ``False`` is used. |
| 345 | 345 |
|
| 346 | 346 |
|
| b/man/gnt-instance.rst | ||
|---|---|---|
| 672 | 672 |
instances. The full path of the directory where the disk files are |
| 673 | 673 |
stored will consist of cluster-wide file storage directory + optional |
| 674 | 674 |
subdirectory + instance name. Example: |
| 675 |
``@RPL_FILE_STORAGE_DIR@``*/mysubdir/instance1.example.com*. This
|
|
| 675 |
``@RPL_FILE_STORAGE_DIR@/mysubdir/instance1.example.com``. This
|
|
| 676 | 676 |
option is only relevant for instances using the file storage backend. |
| 677 | 677 |
|
| 678 | 678 |
The ``--file-driver`` specifies the driver to use for file-based |
| ... | ... | |
| 1600 | 1600 |
instance's runtime before migrating it (eg. ballooning an instance |
| 1601 | 1601 |
down because the target node doesn't have enough available memory). |
| 1602 | 1602 |
|
| 1603 |
If an instance has the backend parameter ``always\_failover`` set to
|
|
| 1603 |
If an instance has the backend parameter ``always_failover`` set to |
|
| 1604 | 1604 |
true, then the migration is automatically converted into a failover. |
| 1605 | 1605 |
|
| 1606 | 1606 |
See **ganeti(7)** for a description of ``--submit`` and other common |
| b/man/hspace.rst | ||
|---|---|---|
| 191 | 191 |
that the computation failed and any values present should not be |
| 192 | 192 |
relied upon. |
| 193 | 193 |
|
| 194 |
Many of the INI_/FIN_ metrics will be also displayed with a TRL_ prefix, |
|
| 195 |
and denote the cluster status at the end of the tiered allocation run. |
|
| 194 |
Many of the ``INI_``/``FIN_`` metrics will be also displayed with a |
|
| 195 |
``TRL_`` prefix, and denote the cluster status at the end of the tiered |
|
| 196 |
allocation run. |
|
| 196 | 197 |
|
| 197 | 198 |
The human output format should be self-explanatory, so it is not |
| 198 | 199 |
described further. |
Also available in: Unified diff