Skip to content

Commit 5bd515d

Browse files
committed
ha-manager: add short section about resources
1 parent 871e1fd commit 5bd515d

File tree

1 file changed

+22
-19
lines changed

1 file changed

+22
-19
lines changed

ha-manager.adoc

Lines changed: 22 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -109,27 +109,36 @@ hard and costly. 'ha-manager' has typical error detection and failover
109109
times of about 2 minutes, so you can get no more than 99.999%
110110
availability.
111111

112+
Requirements
113+
------------
112114

113-
Resources
114-
---------
115+
* at least three cluster nodes (to get reliable quorum)
115116
116-
A resource (sometimes also called service) is uniquely identified by a
117-
service ID (SID) which consists of the service type and an type
118-
specific id, e.g.: 'vm:100'. That example would be a service of type
119-
vm (Virtual machine) with the VMID 100.
117+
* shared storage for VMs and containers
120118
119+
* hardware redundancy (everywhere)
121120
122-
Requirements
123-
------------
121+
* hardware watchdog - if not available we fall back to the
122+
linux kernel software watchdog ('softdog')
124123
125-
* at least three nodes
124+
* optional hardware fencing devices
126125
127-
* shared storage
128126
129-
* hardware redundancy
127+
Resources
128+
---------
129+
130+
We call the primary management unit handled by 'ha-manager' a
131+
resource. A resource (also called "service") is uniquely
132+
identified by a service ID (SID), which consists of the resource type
133+
and an type specific ID, e.g.: 'vm:100'. That example would be a
134+
resource of type 'vm' (virtual machine) with the ID 100.
135+
136+
For now we have two important resources types - virtual machines and
137+
containers. One basic idea here is that we can bundle related software
138+
into such VM or container, so there is no need to compose one big
139+
service from other services, like it was done with 'rgmanager'. In
140+
general, a HA enabled resource should not depend on other resources.
130141

131-
* hardware watchdog - if not available we fall back to the
132-
linux kernel soft dog
133142

134143
How It Works
135144
------------
@@ -284,12 +293,6 @@ If you have a hardware watchdog available remove its module from the blacklist
284293
and restart 'the watchdog-mux' service.
285294

286295

287-
Resource/Service Agents
288-
-------------------------
289-
290-
A resource or also called service can be managed by the
291-
ha-manager. Currently we support virtual machines and container.
292-
293296
Groups
294297
------
295298

0 commit comments

Comments
 (0)