From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Daniel Kral <d.kral@proxmox.com>
Subject: Re: [pve-devel] [PATCH ha-manager 7/9] tests: add test cases for migrating resources with node affinity rules
Date: Mon, 19 Jan 2026 16:00:41 +0100 [thread overview]
Message-ID: <8952a6b2-3498-49c1-9483-49cfe74683e3@proxmox.com> (raw)
In-Reply-To: <20251215155334.476984-8-d.kral@proxmox.com>
Am 15.12.25 um 4:54 PM schrieb Daniel Kral:
> diff --git a/src/test/test-node-affinity-nonstrict7/README b/src/test/test-node-affinity-nonstrict7/README
> new file mode 100644
> index 00000000..35e532cc
> --- /dev/null
> +++ b/src/test/test-node-affinity-nonstrict7/README
> @@ -0,0 +1,9 @@
> +Test whether services in a non-strict node affinity rule handle manual
> +migrations to nodes as expected with respect to whether these are part of the
> +node affinity rule or not.
> +
> +The test scenario is:
> +- vm:101 should be kept on node1 or node3 (preferred)
> +- vm:102 should be kept on node1 or node2 (preferred)
> +- vm:101 is running on node3 with failback enabled
> +- vm:102 is running on node3 with failback disabled
Nit: vm:102 starts out on node2
> diff --git a/src/test/test-node-affinity-strict7/README b/src/test/test-node-affinity-strict7/README
> new file mode 100644
> index 00000000..bc0096f5
> --- /dev/null
> +++ b/src/test/test-node-affinity-strict7/README
> @@ -0,0 +1,9 @@
> +Test whether services in a strict node affinity rule handle manual migrations
> +to nodes as expected with respect to whether these are part of the node
> +affinity rule or not.
> +
> +The test scenario is:
> +- vm:101 must be kept on node1 or node3 (preferred)
> +- vm:102 must be kept on node1 or node2 (preferred)
> +- vm:101 is running on node3 with failback enabled
> +- vm:102 is running on node3 with failback disabled
Nit: vm:102 starts out on node2
_______________________________________________
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:01 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 [this message]
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
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=8952a6b2-3498-49c1-9483-49cfe74683e3@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=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