Browse Source

ha-manager.adoc: improve configuration section

Dietmar Maurer 3 years ago
2 changed files with 49 additions and 7 deletions
  1. +18
  2. +31

+ 18
- 0 View File

@@ -0,0 +1,18 @@

use lib '.';
use strict;
use warnings;
use PVE::RESTHandler;

use Data::Dumper;

use PVE::HA::Resources;

my $private = PVE::HA::Resources::private();
my $properies = $private->{propertyList};
delete $properies->{type};
delete $properies->{sid};

print PVE::RESTHandler::dump_properties($properies);

+ 31
- 7
ha-manager.adoc View File

@@ -269,17 +269,41 @@ quorum, the LRM waits for a new quorum to form. As long as there is no
quorum the node cannot reset the watchdog. This will trigger a reboot
after the watchdog then times out, this happens after 60 seconds.


The HA stack is well integrated in the Proxmox VE API2. So, for
example, HA can be configured via `ha-manager` or the PVE web
interface, which both provide an easy to use tool.
The HA stack is well integrated into the {pve} API. So, for example,
HA can be configured via the `ha-manager` command line interface, or
the {pve} web interface - both interfaces provide an easy way to
manage HA. Automation tools can use the API directly.

All HA configuration files are within `/etc/pve/ha/`, so they get
automatically distributed to the cluster nodes, and all nodes share
the same HA configuration.

The resource configuration file `/etc/pve/ha/resources.cfg` stores
the list of resources managed by `ha-manager`. A resource configuration
inside that list look like this:

<property> <value>

It starts with the service ID followed by a collon. The next lines
contain additional properties:


The HA group configuration file `/etc/pve/ha/groups.cfg` is used to
define groups of cluster nodes. A resource can be restricted to run
only on the members of such group.

The resource configuration file can be located at
`/etc/pve/ha/resources.cfg` and the group configuration file at
`/etc/pve/ha/groups.cfg`. Use the provided tools to make changes,
there shouldn't be any need to edit them manually.

Node Power Status