From: "Daniel Kral" <d.kral@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH ha-manager 9/9] handle node affinity rules with failback in manual migrations
Date: Mon, 19 Jan 2026 16:41:32 +0100 [thread overview]
Message-ID: <DFSOHM22N7TB.OO0ECB65JEOF@proxmox.com> (raw)
In-Reply-To: <1ebb86bc-360c-4ce1-8bea-4e6e3658e85b@proxmox.com>
On Mon Jan 19, 2026 at 4:00 PM CET, Fiona Ebner wrote:
> Am 15.12.25 um 4:55 PM schrieb Daniel Kral:
>> diff --git a/src/PVE/HA/Config.pm b/src/PVE/HA/Config.pm
>> index f8c5965e..fa14816c 100644
>> --- a/src/PVE/HA/Config.pm
>> +++ b/src/PVE/HA/Config.pm
>> @@ -382,22 +382,27 @@ sub service_is_configured {
>> sub get_resource_motion_info {
>> my ($sid) = @_;
>>
>> - my $resources = read_resources_config();
>> + my $conf = read_resources_config();
>
> Nit: maybe it's slightly nicer to use read_and_compile_rules_config()
> already here and avoid a second read call below?
I guess you meant read_and_check_resources_config() here ;)
The service_check_ha_state(...) helper below assumes a parsed section
config (and is used in a bunch of places), while
read_and_check_resources_config() will return a modified version of the
resource config (defaults set, etc.).
What isn't nice at all here is that read_and_compile_rules_config()
reads the manager status and resource config a second and third time and
since it's only used here at the moment I'll make it a private helper
instead of reading on its own.
For read_and_check_resources_config() I'd move out the inner logic into
a separate private helper, so that all of get_resource_motion_info(...)
does work with the same single read from the resource config.
>
>>
>> my $dependent_resources = [];
>> my $blocking_resources_by_node = {};
>>
>> - if (&$service_check_ha_state($resources, $sid)) {
>> + if (&$service_check_ha_state($conf, $sid)) {
>> my $manager_status = read_manager_status();
>> my $ss = $manager_status->{service_status};
>> my $ns = $manager_status->{node_status};
>> # get_resource_motion_info expects a hashset of all nodes with status 'online'
>> my $online_nodes = { map { $ns->{$_} eq 'online' ? ($_ => 1) : () } keys %$ns };
>> + # get_resource_motion_info expects a resource config with defaults set
>> + my $resources = read_and_check_resources_config();
>>
>> my $compiled_rules = read_and_compile_rules_config();
>>
>> + my $cd = $resources->{$sid} // {};
>> ($dependent_resources, $blocking_resources_by_node) =
>> - PVE::HA::Helpers::get_resource_motion_info($ss, $sid, $online_nodes, $compiled_rules);
>> + PVE::HA::Helpers::get_resource_motion_info(
>> + $ss, $sid, $cd, $online_nodes, $compiled_rules,
>> + );
>> }
>>
>> return ($dependent_resources, $blocking_resources_by_node);
_______________________________________________
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-19 15:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 15:52 [pve-devel] [PATCH-SERIES container/ha-manager/manager/qemu-server 00/12] HA node affinity blockers (#1497) Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 1/9] ha: put source files on individual new lines Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 2/9] d/pve-ha-manager.install: remove duplicate Config.pm Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 3/9] config: group and sort use statements Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 4/9] manager: " Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 5/9] manager: report all reasons when resources are blocked from migration Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 6/9] config, manager: factor out resource motion info logic Daniel Kral
2026-01-19 15:00 ` Fiona Ebner
2026-01-19 15:24 ` Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 7/9] tests: add test cases for migrating resources with node affinity rules Daniel Kral
2026-01-19 15:00 ` Fiona Ebner
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 8/9] handle strict node affinity rules in manual migrations Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH ha-manager 9/9] handle node affinity rules with failback " Daniel Kral
2026-01-19 15:00 ` Fiona Ebner
2026-01-19 15:41 ` Daniel Kral [this message]
2025-12-15 15:52 ` [pve-devel] [PATCH qemu-server 1/1] api: migration preconditions: add node affinity as blocking cause Daniel Kral
2026-01-19 15:00 ` Fiona Ebner
2026-01-19 16:55 ` Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH container " Daniel Kral
2025-12-15 15:52 ` [pve-devel] [PATCH manager 1/1] ui: migrate: display precondition messages for ha node affinity Daniel Kral
2026-01-19 15:00 ` [pve-devel] [PATCH-SERIES container/ha-manager/manager/qemu-server 00/12] HA node affinity blockers (#1497) Fiona Ebner
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=DFSOHM22N7TB.OO0ECB65JEOF@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