You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

ha-manager.1-synopsis.adoc 5.8KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224
  1. *ha-manager* `<COMMAND> [ARGS] [OPTIONS]`
  2. *ha-manager add* `<sid>` `[OPTIONS]`
  3. Create a new HA resource.
  4. `<sid>`: `<type>:<name>` ::
  5. HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
  6. `--comment` `<string>` ::
  7. Description.
  8. `--group` `<string>` ::
  9. The HA group identifier.
  10. `--max_relocate` `<integer> (0 - N)` ('default =' `1`)::
  11. Maximal number of service relocate tries when a service failes to start.
  12. `--max_restart` `<integer> (0 - N)` ('default =' `1`)::
  13. Maximal number of tries to restart the service on a node after its start failed.
  14. `--state` `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::
  15. Requested resource state.
  16. `--type` `<ct | vm>` ::
  17. Resource type.
  18. *ha-manager config* `[OPTIONS]`
  19. List HA resources.
  20. `--type` `<ct | vm>` ::
  21. Only list resources of specific type
  22. *ha-manager crm-command migrate* `<sid> <node>`
  23. Request resource migration (online) to another node.
  24. `<sid>`: `<type>:<name>` ::
  25. HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
  26. `<node>`: `<string>` ::
  27. Target node.
  28. *ha-manager crm-command relocate* `<sid> <node>`
  29. Request resource relocatzion to another node. This stops the service on the
  30. old node, and restarts it on the target node.
  31. `<sid>`: `<type>:<name>` ::
  32. HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
  33. `<node>`: `<string>` ::
  34. Target node.
  35. *ha-manager crm-command stop* `<sid> <timeout>`
  36. Request the service to be stopped.
  37. `<sid>`: `<type>:<name>` ::
  38. HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
  39. `<timeout>`: `<integer> (0 - N)` ::
  40. Timeout in seconds. If set to 0 a hard stop will be performed.
  41. *ha-manager groupadd* `<group> --nodes <string>` `[OPTIONS]`
  42. Create a new HA group.
  43. `<group>`: `<string>` ::
  44. The HA group identifier.
  45. `--comment` `<string>` ::
  46. Description.
  47. `--nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
  48. List of cluster node names with optional priority.
  49. `--nofailback` `<boolean>` ('default =' `0`)::
  50. The CRM tries to run services on the node with the highest priority. If a node with higher priority comes online, the CRM migrates the service to that node. Enabling nofailback prevents that behavior.
  51. `--restricted` `<boolean>` ('default =' `0`)::
  52. Resources bound to restricted groups may only run on nodes defined by the group.
  53. `--type` `<group>` ::
  54. Group type.
  55. *ha-manager groupconfig*
  56. Get HA groups.
  57. *ha-manager groupremove* `<group>`
  58. Delete ha group configuration.
  59. `<group>`: `<string>` ::
  60. The HA group identifier.
  61. *ha-manager groupset* `<group>` `[OPTIONS]`
  62. Update ha group configuration.
  63. `<group>`: `<string>` ::
  64. The HA group identifier.
  65. `--comment` `<string>` ::
  66. Description.
  67. `--delete` `<string>` ::
  68. A list of settings you want to delete.
  69. `--digest` `<string>` ::
  70. Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
  71. `--nodes` `<node>[:<pri>]{,<node>[:<pri>]}*` ::
  72. List of cluster node names with optional priority.
  73. `--nofailback` `<boolean>` ('default =' `0`)::
  74. The CRM tries to run services on the node with the highest priority. If a node with higher priority comes online, the CRM migrates the service to that node. Enabling nofailback prevents that behavior.
  75. `--restricted` `<boolean>` ('default =' `0`)::
  76. Resources bound to restricted groups may only run on nodes defined by the group.
  77. *ha-manager help* `[OPTIONS]`
  78. Get help about specified command.
  79. `--extra-args` `<array>` ::
  80. Shows help for a specific command
  81. `--verbose` `<boolean>` ::
  82. Verbose output format.
  83. *ha-manager migrate*
  84. An alias for 'ha-manager crm-command migrate'.
  85. *ha-manager relocate*
  86. An alias for 'ha-manager crm-command relocate'.
  87. *ha-manager remove* `<sid>`
  88. Delete resource configuration.
  89. `<sid>`: `<type>:<name>` ::
  90. HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
  91. *ha-manager set* `<sid>` `[OPTIONS]`
  92. Update resource configuration.
  93. `<sid>`: `<type>:<name>` ::
  94. HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).
  95. `--comment` `<string>` ::
  96. Description.
  97. `--delete` `<string>` ::
  98. A list of settings you want to delete.
  99. `--digest` `<string>` ::
  100. Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
  101. `--group` `<string>` ::
  102. The HA group identifier.
  103. `--max_relocate` `<integer> (0 - N)` ('default =' `1`)::
  104. Maximal number of service relocate tries when a service failes to start.
  105. `--max_restart` `<integer> (0 - N)` ('default =' `1`)::
  106. Maximal number of tries to restart the service on a node after its start failed.
  107. `--state` `<disabled | enabled | ignored | started | stopped>` ('default =' `started`)::
  108. Requested resource state.
  109. *ha-manager status* `[OPTIONS]`
  110. Display HA manger status.
  111. `--verbose` `<boolean>` ('default =' `0`)::
  112. Verbose output. Include complete CRM and LRM status (JSON).