From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <a.zeidler@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 004059E090 for <pve-devel@lists.proxmox.com>; Mon, 30 Oct 2023 12:20:39 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CC6C0E789 for <pve-devel@lists.proxmox.com>; Mon, 30 Oct 2023 12:20:39 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Mon, 30 Oct 2023 12:20:38 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 77D904270A for <pve-devel@lists.proxmox.com>; Mon, 30 Oct 2023 12:20:38 +0100 (CET) From: Alexander Zeidler <a.zeidler@proxmox.com> To: pve-devel@lists.proxmox.com Date: Mon, 30 Oct 2023 12:20:13 +0100 Message-Id: <20231030112013.140969-1-a.zeidler@proxmox.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.032 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 Subject: [pve-devel] [PATCH docs] ha-manager, software updates: add useful BlockIds X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Mon, 30 Oct 2023 11:20:40 -0000 Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com> --- ha-manager.adoc | 5 +++++ system-software-updates.adoc | 1 + 2 files changed, 6 insertions(+) diff --git a/ha-manager.adoc b/ha-manager.adoc index 8390782..53330a1 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -260,6 +260,7 @@ This all gets supervised by the CRM which currently holds the manager master lock. +[[ha_manager_service_states]] Service States ~~~~~~~~~~~~~~ @@ -352,6 +353,7 @@ disabled:: Service is stopped and marked as `disabled` +[[ha_manager_lrm]] Local Resource Manager ~~~~~~~~~~~~~~~~~~~~~~ @@ -416,6 +418,8 @@ what both daemons, the LRM and the CRM, did. You may use `journalctl -u pve-ha-lrm` on the node(s) where the service is and the same command for the pve-ha-crm on the node which is the current master. + +[[ha_manager_crm]] Cluster Resource Manager ~~~~~~~~~~~~~~~~~~~~~~~~ @@ -834,6 +838,7 @@ this is not the case the update process can take too long which, in the worst case, may result in a reset triggered by the watchdog. +[[ha_manager_node_maintenance]] Node Maintenance ---------------- diff --git a/system-software-updates.adoc b/system-software-updates.adoc index 013e171..471ff1e 100644 --- a/system-software-updates.adoc +++ b/system-software-updates.adoc @@ -1,3 +1,4 @@ +[[system_software_updates]] System Software Updates ----------------------- ifdef::wiki[] -- 2.39.2