From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH ha-manager 0/7] Some pve-ha-simulator fixups
Date: Mon, 17 Nov 2025 18:20:59 +0100 [thread overview]
Message-ID: <20251117172147.533969-1-d.kral@proxmox.com> (raw)
These are a few patches to fix some things that popped up with the
recent changes for the pve-ha-simulator.
PATCH 1 smaller cleanup
PATCH 2-4 fix r/w, add default fallback, fix creating new HA
resources in pve-ha-simulator with static service stats
PATCH 5 remove static_service_stats print statements
PATCH 6 delete static_service_stats on service deletion
PATCH 7 fix pve-ha-simulator being runnable on non-PVE envs
I tested the following things on the upstream pve-ha-simulator:
* creating new HA resources
* updating HA resources
* deleting HA resources
* re-creating HA resources with same sid
* saving and restoring state of the HA Simulator
* switching back and forth between basic and static load scheduler
* migrating/relocating HA resources in the HA Simulator
* doing all of the above on a standalone non-PVE environment:
* switching to 'static' will make the HA Simulator fallback to
'basic' as expected
As also stated in a patch message, it would be great to split the
fallback values out to the RTHardware alone, so that no future test
cases accidentally rely on those being set.
Daniel Kral (7):
sim: hardware: remove service default groups
sim: fix read and write to static service stats' maxmem
sim: hardware: initialize default fallback static_service_stats
sim: hardware: fix ha resource existence check in
set_static_service_stats
sim: hardware: do not print stat changes in set_static_service_stats
sim: hardware: delete static service stats on service deletion
d/rules: add new PVE dependencies from PVE::Tools to pve-ha-simulator
debian/rules | 2 ++
src/PVE/HA/Sim/Hardware.pm | 40 ++++++++++++++++++++++--------------
src/PVE/HA/Sim/RTHardware.pm | 11 +++++-----
3 files changed, 32 insertions(+), 21 deletions(-)
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-11-17 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 17:20 Daniel Kral [this message]
2025-11-17 17:21 ` [pve-devel] [PATCH ha-manager 1/7] sim: hardware: remove service default groups Daniel Kral
2025-11-17 17:21 ` [pve-devel] [PATCH ha-manager 2/7] sim: fix read and write to static service stats' maxmem Daniel Kral
2025-11-17 17:21 ` [pve-devel] [PATCH ha-manager 3/7] sim: hardware: initialize default fallback static_service_stats Daniel Kral
2025-11-17 17:21 ` [pve-devel] [PATCH ha-manager 4/7] sim: hardware: fix ha resource existence check in set_static_service_stats Daniel Kral
2025-11-17 17:21 ` [pve-devel] [PATCH ha-manager 5/7] sim: hardware: do not print stat changes " Daniel Kral
2025-11-17 17:21 ` [pve-devel] [PATCH ha-manager 6/7] sim: hardware: delete static service stats on service deletion Daniel Kral
2025-11-17 17:21 ` [pve-devel] [PATCH ha-manager 7/7] d/rules: add new PVE dependencies from PVE::Tools to pve-ha-simulator Daniel Kral
2025-11-17 21:37 ` [pve-devel] applied: [PATCH ha-manager 0/7] Some pve-ha-simulator fixups 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=20251117172147.533969-1-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