mirror of
https://git.proxmox.com/git/pve-docs
synced 2025-06-15 19:57:33 +00:00
ha-manager: add short section about resources
This commit is contained in:
parent
871e1fd656
commit
5bd515d441
@ -109,27 +109,36 @@ hard and costly. 'ha-manager' has typical error detection and failover
|
|||||||
times of about 2 minutes, so you can get no more than 99.999%
|
times of about 2 minutes, so you can get no more than 99.999%
|
||||||
availability.
|
availability.
|
||||||
|
|
||||||
|
Requirements
|
||||||
|
------------
|
||||||
|
|
||||||
|
* at least three cluster nodes (to get reliable quorum)
|
||||||
|
|
||||||
|
* shared storage for VMs and containers
|
||||||
|
|
||||||
|
* hardware redundancy (everywhere)
|
||||||
|
|
||||||
|
* hardware watchdog - if not available we fall back to the
|
||||||
|
linux kernel software watchdog ('softdog')
|
||||||
|
|
||||||
|
* optional hardware fencing devices
|
||||||
|
|
||||||
|
|
||||||
Resources
|
Resources
|
||||||
---------
|
---------
|
||||||
|
|
||||||
A resource (sometimes also called service) is uniquely identified by a
|
We call the primary management unit handled by 'ha-manager' a
|
||||||
service ID (SID) which consists of the service type and an type
|
resource. A resource (also called "service") is uniquely
|
||||||
specific id, e.g.: 'vm:100'. That example would be a service of type
|
identified by a service ID (SID), which consists of the resource type
|
||||||
vm (Virtual machine) with the VMID 100.
|
and an type specific ID, e.g.: 'vm:100'. That example would be a
|
||||||
|
resource of type 'vm' (virtual machine) with the ID 100.
|
||||||
|
|
||||||
|
For now we have two important resources types - virtual machines and
|
||||||
|
containers. One basic idea here is that we can bundle related software
|
||||||
|
into such VM or container, so there is no need to compose one big
|
||||||
|
service from other services, like it was done with 'rgmanager'. In
|
||||||
|
general, a HA enabled resource should not depend on other resources.
|
||||||
|
|
||||||
Requirements
|
|
||||||
------------
|
|
||||||
|
|
||||||
* at least three nodes
|
|
||||||
|
|
||||||
* shared storage
|
|
||||||
|
|
||||||
* hardware redundancy
|
|
||||||
|
|
||||||
* hardware watchdog - if not available we fall back to the
|
|
||||||
linux kernel soft dog
|
|
||||||
|
|
||||||
How It Works
|
How It Works
|
||||||
------------
|
------------
|
||||||
@ -284,12 +293,6 @@ If you have a hardware watchdog available remove its module from the blacklist
|
|||||||
and restart 'the watchdog-mux' service.
|
and restart 'the watchdog-mux' service.
|
||||||
|
|
||||||
|
|
||||||
Resource/Service Agents
|
|
||||||
-------------------------
|
|
||||||
|
|
||||||
A resource or also called service can be managed by the
|
|
||||||
ha-manager. Currently we support virtual machines and container.
|
|
||||||
|
|
||||||
Groups
|
Groups
|
||||||
------
|
------
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user