From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] ha-manager, software updates: add useful BlockIds
Date: Mon, 30 Oct 2023 12:20:13 +0100 [thread overview]
Message-ID: <20231030112013.140969-1-a.zeidler@proxmox.com> (raw)
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
next reply other threads:[~2023-10-30 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 11:20 Alexander Zeidler [this message]
2023-10-30 13:09 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231030112013.140969-1-a.zeidler@proxmox.com \
--to=a.zeidler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal