From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 common/docs/widget-toolkit/manager/firewall 0/6] drop vmbr prefix for bridges
Date: Fri, 23 Feb 2024 15:36:45 +0100 [thread overview]
Message-ID: <20240223143651.418065-1-s.hanreich@proxmox.com> (raw)
Original patch series by Jillian Morgan <jillian.morgan@primordial.ca>
Changes from v1 -> v2:
* limit name to 15 characters
* properly validate bridge names in vlan/qinq zones
* properly handle OVS bridges
* handle new bridge names in firewall simulator
common:
Stefan Hanreich (1):
interfaces: allow arbitrary bridge names in network config
src/PVE/INotify.pm | 24 +++++++++++-------------
1 file changed, 11 insertions(+), 13 deletions(-)
docs:
Stefan Hanreich (1):
network: update specification for bridge names
pve-network.adoc | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
widget-toolkit:
Stefan Hanreich (1):
network: allow bridges to have any valid interface name
src/Toolkit.js | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
manager:
Stefan Hanreich (2):
sdn: qinq: vlan: properly validate bridge name
sdn: vlan: fix indentation in vlan edit dialogue
www/manager6/sdn/zones/QinQEdit.js | 3 +++
www/manager6/sdn/zones/VlanEdit.js | 11 +++++++----
2 files changed, 10 insertions(+), 4 deletions(-)
firewall:
Stefan Hanreich (1):
simulator: use new bridge naming scheme
src/PVE/FirewallSimulator.pm | 20 ++++++++++----------
src/PVE/Service/pve_firewall.pm | 4 ++--
2 files changed, 12 insertions(+), 12 deletions(-)
Summary over all repositories:
7 files changed, 44 insertions(+), 37 deletions(-)
--
murpp v0.4.0
next reply other threads:[~2024-02-23 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 14:36 Stefan Hanreich [this message]
2024-02-23 14:36 ` [pve-devel] [PATCH v2 common 1/6] interfaces: allow arbitrary bridge names in network config Stefan Hanreich
2024-02-23 14:36 ` [pve-devel] [PATCH v2 docs 2/6] network: update specification for bridge names Stefan Hanreich
2024-02-23 14:36 ` [pve-devel] [PATCH v2 widget-toolkit 3/6] network: allow bridges to have any valid interface name Stefan Hanreich
2024-02-23 14:36 ` [pve-devel] [PATCH v2 manager 4/6] sdn: qinq: vlan: properly validate bridge name Stefan Hanreich
2024-02-23 14:36 ` [pve-devel] [PATCH v2 manager 5/6] sdn: vlan: fix indentation in vlan edit dialogue Stefan Hanreich
2024-02-23 14:36 ` [pve-devel] [PATCH v2 firewall 6/6] simulator: use new bridge naming scheme Stefan Hanreich
[not found] ` <mailman.235.1708944723.434.pve-devel@lists.proxmox.com>
2024-02-26 15:36 ` Thomas Lamprecht
2024-02-27 12:35 ` Stefan Hanreich
2024-02-28 9:35 ` 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=20240223143651.418065-1-s.hanreich@proxmox.com \
--to=s.hanreich@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