From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH ha-manager v2 10/12] config: factor out checked_resources_config helper
Date: Tue, 20 Jan 2026 16:27:42 +0100 [thread overview]
Message-ID: <20260120152755.499037-11-d.kral@proxmox.com> (raw)
In-Reply-To: <20260120152755.499037-1-d.kral@proxmox.com>
This allows future users to retrieve the checked resource config if
these already have a parsed resource config instead of reading it twice.
Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
changes v1 -> v2:
- new!
src/PVE/HA/Config.pm | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/src/PVE/HA/Config.pm b/src/PVE/HA/Config.pm
index d01b43d8..7607b194 100644
--- a/src/PVE/HA/Config.pm
+++ b/src/PVE/HA/Config.pm
@@ -105,10 +105,9 @@ sub read_resources_config {
return cfs_read_file($ha_resources_config);
}
-# checks if resource exists and sets defaults for unset values
-sub read_and_check_resources_config {
-
- my $cfg = cfs_read_file($ha_resources_config);
+# returns resources config with defaults and node placement set
+my sub checked_resources_config {
+ my ($cfg) = @_;
my $vmlist = PVE::Cluster::get_vmlist();
my $resources = {};
@@ -137,6 +136,13 @@ sub read_and_check_resources_config {
return wantarray ? ($resources, $cfg->{digest}) : $resources;
}
+# checks if resource exists and sets defaults for unset values
+sub read_and_check_resources_config {
+ my $cfg = cfs_read_file($ha_resources_config);
+
+ return checked_resources_config($cfg);
+}
+
my sub update_single_resource_config_inplace {
my ($cfg, $sid, $param, $delete) = @_;
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2026-01-20 15:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 15:27 [pve-devel] [PATCH-SERIES container/ha-manager/manager/qemu-server v2 00/15] HA node affinity blockers (#1497) Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 01/12] ha: put source files on individual new lines Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 02/12] d/pve-ha-manager.install: remove duplicate Config.pm Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 03/12] config: group and sort use statements Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 04/12] manager: " Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 05/12] manager: report all reasons when resources are blocked from migration Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 06/12] config, manager: factor out resource motion info logic Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 07/12] tests: add test cases for migrating resources with node affinity rules Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 08/12] handle strict node affinity rules in manual migrations Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 09/12] config: improve variable names in read_and_check_resources_config Daniel Kral
2026-01-20 15:27 ` Daniel Kral [this message]
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 11/12] handle node affinity rules with failback in manual migrations Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH ha-manager v2 12/12] config: remove duplicate config reads in get_resource_motion_info Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH qemu-server v2 1/1] api: migration preconditions: add node affinity as blocking cause Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH container " Daniel Kral
2026-01-20 15:27 ` [pve-devel] [PATCH manager v2 1/1] ui: migrate: display precondition messages for ha node affinity Daniel Kral
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=20260120152755.499037-11-d.kral@proxmox.com \
--to=d.kral@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox