From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH ha-manager v2 06/18] rules: make rules sorting optional in foreach_rule helper
Date: Tue, 9 Sep 2025 10:33:43 +0200 [thread overview]
Message-ID: <20250909083539.39675-7-d.kral@proxmox.com> (raw)
In-Reply-To: <20250909083539.39675-1-d.kral@proxmox.com>
Most users of the foreach_rule helper are agnostic to the iteration
order of the rules and as sorting can become a non-neglible overhead for
larger rule sets, make sorting rules optional.
The only caller dependent on a sorted rule set is the rules' index API
endpoint.
Signed-off-by: Daniel Kral <d.kral@proxmox.com>
Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>
Tested-by: Michael Köppl <m.koeppl@proxmox.com>
---
no changes since v1
src/PVE/API2/HA/Rules.pm | 1 +
src/PVE/HA/Rules.pm | 10 ++++++----
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/PVE/API2/HA/Rules.pm b/src/PVE/API2/HA/Rules.pm
index ab431019..fb8b465b 100644
--- a/src/PVE/API2/HA/Rules.pm
+++ b/src/PVE/API2/HA/Rules.pm
@@ -194,6 +194,7 @@ __PACKAGE__->register_method({
},
type => $type,
sid => $resource,
+ sorted => 1,
);
return $res;
diff --git a/src/PVE/HA/Rules.pm b/src/PVE/HA/Rules.pm
index e13769a1..784f2d36 100644
--- a/src/PVE/HA/Rules.pm
+++ b/src/PVE/HA/Rules.pm
@@ -428,7 +428,7 @@ Filters the given C<$rules> according to the C<$opts> and loops over the
resulting rules in the order as defined in the section config and executes
C<$func> with the parameters C<L<< ($rule, $ruleid) >>>.
-The following key-value pairs for C<$opts> as filter properties are:
+The following key-value pairs for C<$opts> are:
=over
@@ -438,6 +438,8 @@ The following key-value pairs for C<$opts> as filter properties are:
=item C<$exclude_disabled_rules>: Limits C<$rules> to those which are enabled.
+=item C<$sorted>: Sorts C<$rules> according to C<< $rules->{order} >>.
+
=back
=cut
@@ -447,9 +449,9 @@ sub foreach_rule : prototype($$;%) {
my $sid = $opts{sid};
- my @ruleids = sort {
- $rules->{order}->{$a} <=> $rules->{order}->{$b}
- } keys %{ $rules->{ids} };
+ my @ruleids = keys $rules->{ids}->%*;
+ @ruleids = sort { $rules->{order}->{$a} <=> $rules->{order}->{$b} } @ruleids
+ if defined($opts{sorted});
for my $ruleid (@ruleids) {
my $rule = $rules->{ids}->{$ruleid};
--
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:[~2025-09-09 8:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 8:33 [pve-devel] [PATCH ha-manager v2 00/18] HA rules fixes + cleanup + performance improvements Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 01/18] config: do not add ignored resources to dependent resources Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 02/18] manager: retranslate rules if nodes are added or removed Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 03/18] rules: factor out disjoint rules' resource set helper Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 04/18] rules: resource affinity: inter-consistency check with merged positive rules Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 05/18] rules: add merged positive resource affinity info in global checks Daniel Kral
2025-09-09 8:33 ` Daniel Kral [this message]
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 07/18] rename rule's canonicalize stage to transform stage Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 08/18] rules: make plugins register transformers instead of plugin_transform Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 09/18] rules: node affinity: decouple get_node_affinity helper from Usage class Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 10/18] compile ha rules to a more compact representation Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 11/18] test: rules: use to_json instead of Data::Dumper for config output Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 12/18] test: rules: add compiled config output to rules config test cases Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 13/18] rules: node affinity: define node priority outside hash access Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 14/18] move minimum version check helper to ha tools Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 15/18] manager: move group migration cooldown variable into helper Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 16/18] api: status: sync active service counting with lrm's helper Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 17/18] manager: group migration: " Daniel Kral
2025-09-09 8:33 ` [pve-devel] [PATCH ha-manager v2 18/18] factor out counting of active services into helper 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=20250909083539.39675-7-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