From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-network v3 26/45] sdn: microseg: add name regex matcher
Date: Tue, 27 Oct 2026 09:55:08 +0100 [thread overview]
Message-ID: <20261027085527.702738-27-h.laimer@proxmox.com> (raw)
In-Reply-To: <20261027085527.702738-1-h.laimer@proxmox.com>
A name regex matcher binds every guest whose name matches a regular
expression. For a container the name is its hostname.
A rename into or out of the names a matcher covers moves the guest
between groups. So a check for renames asks for SDN.Use on
/sdn/microseg, like the one for tag changes.
Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
---
src/PVE/Network/SDN/Microseg.pm | 43 +++++++++++++++++++++++++++++----
1 file changed, 38 insertions(+), 5 deletions(-)
diff --git a/src/PVE/Network/SDN/Microseg.pm b/src/PVE/Network/SDN/Microseg.pm
index 8090043268a7..bdfde447b320 100644
--- a/src/PVE/Network/SDN/Microseg.pm
+++ b/src/PVE/Network/SDN/Microseg.pm
@@ -32,9 +32,18 @@ PVE::JSONSchema::register_standard_option(
},
);
+PVE::JSONSchema::register_format(
+ 'pve-sdn-microseg-name-regex',
+ sub {
+ my ($regex) = @_;
+ die "name regex '$regex' contains non-ASCII characters\n" if $regex =~ m/[^\x00-\x7f]/;
+ return $regex;
+ },
+);
+
cfs_register_file('sdn/microseg.cfg', \&parse_microseg_config, \&write_microseg_config);
-our $ASSIGNMENT_TYPES = ['guest-assignment', 'tag-assignment'];
+our $ASSIGNMENT_TYPES = ['guest-assignment', 'tag-assignment', 'regex-assignment'];
sub parse_microseg_config {
my ($filename, $raw) = @_;
@@ -203,7 +212,8 @@ sub assignment_properties {
type => 'string',
enum => $ASSIGNMENT_TYPES,
description => "The matcher kind. 'guest-assignment' binds a specific guest,"
- . " 'tag-assignment' every guest carrying the matched tags.",
+ . " 'tag-assignment' every guest carrying the matched tags, 'regex-assignment'"
+ . " every guest whose name matches a regex.",
};
$properties->{vmid} = get_standard_option(
'pve-vmid',
@@ -234,6 +244,17 @@ sub assignment_properties {
description => "How tags match. 'any' shares a listed tag, 'all' carries every"
. " listed tag, 'exact' equals the listed set.",
};
+ $properties->{'name-regex'} = {
+ type => 'string',
+ format => 'pve-sdn-microseg-name-regex',
+ minLength => 1,
+ maxLength => 1024,
+ 'type-property' => 'type',
+ 'instance-types' => ['regex-assignment'],
+ description => "A regular expression matched against each guest's name, ASCII only."
+ . " It matches anywhere in the name, so anchor it with '^' and '\$' for a"
+ . " whole-name match. A guest without a name is never matched.",
+ };
$properties->{iface} = {
type => 'integer',
minimum => 0,
@@ -294,11 +315,22 @@ sub check_tag_access {
}
}
+# a rename that changes which regex assignments match can move the guest between groups like a
+# tag change, so it needs SDN.Use on the policy. The match runs in the config, so it uses the
+# regex engine that resolves the NICs.
+sub check_name_access {
+ my ($rpcenv, $authuser, $old, $new) = @_;
+
+ return if !config()->name_match_changed($old, $new);
+ $rpcenv->check($authuser, '/sdn/microseg', ['SDN.Use']);
+}
+
sub guest_inventory {
my (%opts) = @_;
- # the data plane takes a guest's NICs from the node, so an apply leaves them out
- my @props = ('tags', $opts{skip_nics} ? () : map { "net$_" } 0 .. $MAX_NIC_INDEX);
+ # the data plane takes a guest's NICs from the node
+ my @props =
+ ('tags', 'name', 'hostname', $opts{skip_nics} ? () : map { "net$_" } 0 .. $MAX_NIC_INDEX);
my $by_vmid = PVE::Cluster::get_guest_config_properties(\@props, $opts{vmid});
@@ -313,6 +345,7 @@ sub guest_inventory {
push @$inventory,
{
vmid => $vmid,
+ name => $guest->{name} // $guest->{hostname},
tags => \@tags,
nics => \@nics,
};
@@ -341,7 +374,7 @@ my sub parse_guest_nic {
return $iface =~ m/^(?:tap|veth)(\d+)i(\d+)$/;
}
-# the guest as the inventory lists it, with nothing but its vmid when it has no tags
+# the inventory leaves out a guest without tags and name
my sub guest_info {
my ($vmid) = @_;
--
2.47.3
next prev parent reply other threads:[~2026-10-27 8:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 8:54 [PATCH access-control/cluster/container/docs/manager/network/proxmox{-ebpf,-ve-rs,-perl-rs}/qemu-server v3 00/45] sdn: add microsegmentation support Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ebpf v3 01/45] build: keep the build directory out of the BPF objects Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ebpf v3 02/45] policy: add the enforcement subsystem for guest interfaces Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ebpf v3 03/45] policy: add a check for non-first fragments Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 04/45] ve-config: firewall: add a constructor for sctp matches Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 05/45] ve-config: sdn: microseg: add identity allocation for group sets Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 06/45] ve-config: sdn: microseg: add config types Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 07/45] ve-config: sdn: microseg: add tag matcher Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 08/45] ve-config: sdn: microseg: add name regex matcher Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 09/45] ve-config: sdn: microseg: narrow rules by protocol and ports Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 10/45] ve-config: sdn: microseg: add group hierarchy Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 11/45] ve-config: firewall: expose protocol, icmp type and code numbers Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 12/45] ve-config: sdn: microseg: add the desired state Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 13/45] microseg: add a crate that applies the policy to a node's guest NICs Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-ve-rs v3 14/45] microseg: add a rule option that matches non-first fragments Hannes Laimer
2026-10-27 8:54 ` [PATCH pve-cluster v3 15/45] cfs: add 'sdn/microseg.cfg' to observed files Hannes Laimer
2026-10-27 8:54 ` [PATCH pve-access-control v3 16/45] permissions: add ACL path for SDN microsegmentation Hannes Laimer
2026-10-27 8:54 ` [PATCH proxmox-perl-rs v3 17/45] pve-rs: sdn: add microseg config binding Hannes Laimer
2026-10-27 8:55 ` [PATCH proxmox-perl-rs v3 18/45] pve-rs: sdn: microseg: bind the data plane Hannes Laimer
2026-10-27 8:55 ` [PATCH proxmox-perl-rs v3 19/45] pve-rs: sdn: microseg: check the data plane limits on render Hannes Laimer
2026-10-27 8:55 ` [PATCH proxmox-perl-rs v3 20/45] pve-rs: debian: fire the pve-microseg-update trigger on upgrade Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-network v3 21/45] sdn: zones: add vxlan-gbp option to vxlan and evpn zones Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-network v3 22/45] sdn: microseg: add config, API and guest inventory Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-network v3 23/45] sdn: dry-run: show pending microseg changes Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-network v3 24/45] sdn: microseg: enforce the policy on guest NICs Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-network v3 25/45] sdn: microseg: add tag matcher Hannes Laimer
2026-10-27 8:55 ` Hannes Laimer [this message]
2026-10-27 8:55 ` [PATCH pve-network v3 27/45] sdn: microseg: add an update for a running NIC Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-network v3 28/45] sdn: microseg: expose protocol, port and macro rule options Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-network v3 29/45] sdn: microseg: allow nesting groups under a parent Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-network v3 30/45] sdn: microseg: expose the fragments rule option Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 31/45] network: apply the microseg policy on reload Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 32/45] pve-sdn-commit: apply the microseg policy at boot Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 33/45] ui: sdn: zones: add vxlan-gbp checkbox to vxlan and evpn Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 34/45] ui: sdn: add microsegmentation panel Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 35/45] ui: sdn: dry-run: show pending microseg diff Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 36/45] ui: sdn: microseg: add tag matcher Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 37/45] ui: sdn: microseg: add name regex matcher Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 38/45] ui: sdn: microseg: add narrowing to the rule form Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 39/45] ui: sdn: microseg: show and edit the group hierarchy Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 40/45] ui: sdn: microseg: add fragments option to the rule form Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-manager v3 41/45] ui: sdn: microseg: add a guest tab with its groups and rules Hannes Laimer
2026-10-27 8:55 ` [PATCH qemu-server v3 42/45] network: update the microseg enforcement on a tag or name change Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-container v3 43/45] lxc: update the microseg enforcement on a tag or hostname change Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-docs v3 44/45] sdn: zones: document the VXLAN-GBP option Hannes Laimer
2026-10-27 8:55 ` [PATCH pve-docs v3 45/45] sdn: add microsegmentation section Hannes Laimer
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=20261027085527.702738-27-h.laimer@proxmox.com \
--to=h.laimer@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