From: David Riley <d.riley@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH access-control/network v5 0/7] fix #7520: sdn: prune orphaned ACLs and handle VNet migrations
Date: Tue, 7 Jul 2026 14:03:57 +0200 [thread overview]
Message-ID: <20260707120404.73072-1-d.riley@proxmox.com> (raw)
Thanks @Daniel K. for the thorough review.
Difference from v4:
* Instead of passing arrays of path segments [<zone>, <vnet>], paths
are now passed as strings <zone>/<vnet> to match the actual ACL
paths as there was no real benefit of using arrays.
* Moved helper functions into seperate commits and updated the commit
messages accordingly.
* Fix: style nits (post if, for loop dereferencing, ...)
* Fix: tests nits (grouped mocking, removed main subroutine)
Difference from v3:
* Refactored tests
* Perl style guide refactor (for instead of foreach)
* Update: route_map_suffix regex used for detecting digits to match
style guide recommendation
Difference from v2:
* Relocate VNet ACLs to the new zone path when a VNet is moved,
including a validation check to abort on path conflicts.
* Refactor diff generation in preparation for an upcoming patch
series, resolving #7294 [0]. The upcoming series will hook into the
VNet diff to clean up pool members.
* Add unit testing for pruning and migration mechanism
=== Original Cover Letter ===
Implement a pruning mechanism to clean up orphaned SDN ACL entries by
comparing the running configuration with the newly compiled state
during configuration commit.
This ensures state consistency for manual applies via the UI/API
as well as during the automatic configuration reload on system boot.
The pruning covers:
* Zones
* VNets
* Fabrics
* Controllers
* Route maps
* Prefix lists
IPAMs and DNS are excluded as they are not staged.
Link: https://bugzilla.proxmox.com/show_bug.cgi?id=7520
[0] https://bugzilla.proxmox.com/show_bug.cgi?id=7294
pve-access-control:
David Riley (6):
permission: add acl tree node parent lookup without node creation
fix #7520: sdn: add pruning SDN resources ACLs
test: add sdn acl pruning tests
permission: add helper to check for active permissions
fix #7520: sdn: add VNet ACL migration
test: add sdn acl migration tests
src/PVE/AccessControl.pm | 155 ++++++++++++++++++++++++++
src/test/Makefile | 3 +
src/test/sdn_acl_migration_test.pl | 171 +++++++++++++++++++++++++++++
src/test/sdn_acl_pruning_test.pl | 134 ++++++++++++++++++++++
4 files changed, 463 insertions(+)
create mode 100644 src/test/sdn_acl_migration_test.pl
create mode 100644 src/test/sdn_acl_pruning_test.pl
pve-network:
David Riley (1):
fix #7520: config: prune orphaned and relocate moved VNet ACLs
src/PVE/Network/SDN.pm | 115 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 115 insertions(+)
Summary over all repositories:
5 files changed, 578 insertions(+), 0 deletions(-)
--
Generated by murpp 0.11.0
next reply other threads:[~2026-07-07 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 12:03 David Riley [this message]
2026-07-07 12:03 ` [PATCH pve-access-control v5 1/7] permission: add acl tree node parent lookup without node creation David Riley
2026-07-07 12:03 ` [PATCH pve-access-control v5 2/7] fix #7520: sdn: add pruning SDN resources ACLs David Riley
2026-07-07 12:04 ` [PATCH pve-access-control v5 3/7] test: add sdn acl pruning tests David Riley
2026-07-07 12:04 ` [PATCH pve-access-control v5 4/7] permission: add helper to check for active permissions David Riley
2026-07-07 12:04 ` [PATCH pve-access-control v5 5/7] fix #7520: sdn: add VNet ACL migration David Riley
2026-07-07 12:04 ` [PATCH pve-access-control v5 6/7] test: add sdn acl migration tests David Riley
2026-07-07 12:04 ` [PATCH pve-network v5 7/7] fix #7520: config: prune orphaned and relocate moved VNet ACLs David Riley
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=20260707120404.73072-1-d.riley@proxmox.com \
--to=d.riley@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