public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Daniel Kral" <d.kral@proxmox.com>
To: "Fiona Ebner" <f.ebner@proxmox.com>,
	"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH ha-manager 6/9] config, manager: factor out resource motion info logic
Date: Tue, 20 Jan 2026 11:37:21 +0100	[thread overview]
Message-ID: <DFTCN9FMGI4N.8N6064Q2QLNI@proxmox.com> (raw)
In-Reply-To: <97862bcf-38f4-49d7-b0aa-c31293343386@proxmox.com>

On Tue Jan 20, 2026 at 10:35 AM CET, Fiona Ebner wrote:
> Am 20.01.26 um 10:25 AM schrieb Daniel Kral:
>> Oh wait, just noticed that this would create a circular dependency,
>> because get_resource_motion_info(...) uses get_affinitive_resources(...)
>> from PVE::HA::Rules::ResourceAffinity, and
>> PVE::HA::Rules::ResourceAffinity in turn uses PVE::HA::Rules::Helpers
>> again..
>> 
>> I'd tend to let get_resource_motion_info(...) stay in PVE::HA::Helpers,
>> or do you have other ideas?
>
> Okay, so get_resource_motion_info() depends on:
> PVE::HA::Rules::NodeAffinity
> PVE::HA::Rules::ResourceAffinity
>
> And in fact, having a PVE::HA::Helpers depend on those two seems bad for
> moving forward, because it means that those two modules won't be able to
> use PVE::HA::Helpers without creating a circular dependency. Ideally,
> the PVE::HA::Helpers module would not have such dependencies and be
> usable from essentially any other HA module.
>
> So considering the two dependencies, what about putting
> get_resource_motion_info() in PVE::HA::Rules itself? It is a more
> top-level function that depends on the rule submodules, so that seems to
> be a fitting place.

As discussed off-list, unfortunately get_resource_motion_info(...)
cannot be moved to PVE::HA::Rules that easily because it is the base
plugin for PVE::HA::Rules::{NodeAffinity,ResourceAffinity} and therefore
cannot depend on them either..

@Fiona suggested that in the long-term it would be great to split the
plugin-related parts of PVE::HA::Rules out into PVE::HA::Rules::Plugin,
which would make it easier to encapsulate the Rules module, but we
agreed to postpone it to its own patch series.

For now, since PVE::HA::Tools already exists as a module to have
helpers, which do not have any inner HA-related dependencies, we agreed
that PVE::HA::Helpers would be fine as a helper module with HA
dependencies.. albeit I still might change the name to something more
telling in a v2.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2026-01-20 10:37 UTC|newest]

Thread overview: 27+ 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
2026-01-20  9:25       ` Daniel Kral
2026-01-20  9:35         ` Fiona Ebner
2026-01-20 10:37           ` Daniel Kral [this message]
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
2026-01-20  9:52       ` Fiona Ebner
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
2026-01-20  9:07       ` Fiona Ebner
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
2026-01-20 15:33 ` [pve-devel] superseded: " 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=DFTCN9FMGI4N.8N6064Q2QLNI@proxmox.com \
    --to=d.kral@proxmox.com \
    --cc=f.ebner@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal