From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 2E1761FF136 for ; Mon, 04 May 2026 13:12:41 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 624DE1A602; Mon, 4 May 2026 13:12:38 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs 1/2] ha-manager: reword ha resources section Date: Mon, 4 May 2026 13:11:54 +0200 Message-ID: <20260504111159.183163-2-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260504111159.183163-1-d.kral@proxmox.com> References: <20260504111159.183163-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777893018472 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.078 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: GWDUCCZBNWAFRAQ4FHY5ODDYB4QAWD6O X-Message-ID-Hash: GWDUCCZBNWAFRAQ4FHY5ODDYB4QAWD6O X-MailFrom: d.kral@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Focus on the introduction of the HA resource concept first and what an HA resource represents in the broader Proxmox VE context, while introducing the service ID only in a later chapter. Remove the comparison with `rgmanager` as it's quite dated already and seemingly unused as it seems to be replaced by pacemaker in newer versions of RHEL. Signed-off-by: Daniel Kral --- ha-manager.adoc | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index a1b2210..6bf4e69 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -126,18 +126,14 @@ the linux kernel software watchdog (`softdog`). Resources --------- -We call the primary management unit handled by `ha-manager` a -resource. A resource (also called ``service'') is uniquely -identified by a service ID (SID), which consists of the resource type -and a type specific ID, for example `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 a VM or container, so there is no need to compose one big -service from other services, as was done with `rgmanager`. In -general, a HA managed resource should not depend on other resources. +The HA Manager's primary management unit is called an HA resource (or +``HA service''). Currently, an HA resource can be either a Virtual +Machine (VM) or Linux Containers (CT). +Each HA resource is uniquely identified by a service ID (`sid`), which +consists of the resource type and a type-specific ID, which is the VMID +for VMs and containers. For example, for the VM with VMID `100`, the +service ID is `vm:100`. Management Tasks ---------------- -- 2.47.3