From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH common/docs/firewall/manager/proxmox-widget-toolkit v4 0/6] drop vmbr prefix for bridges
Date: Sun, 21 Apr 2024 14:19:30 +0200 [thread overview]
Message-ID: <b5c3fdbb-2e61-40ee-b5db-3a8aa3534271@proxmox.com> (raw)
In-Reply-To: <20240412080737.34521-1-s.hanreich@proxmox.com>
Am 12/04/2024 um 10:07 schrieb Stefan Hanreich:
> Original patch series by Jillian Morgan <jillian.morgan@primordial.ca>
>
> I've refrained from adding arbitrary bond names in this patch series, since
> that would require a bigger amount of changes in the firewall simulator. I'll
> look into adding that in a future patch series.
>
> Dependencies:
> * pve-manager requires proxmox-widget-toolkit & pve-common
> * pve-firewall requires pve-common
>
> Changes from v3 -> v4:
> * Improved wording of the documentation (thanks @Fabian!)
> * added information about dependencies
>
> Changes from v2 -> v3:
> * limit bridge names to 10 characters in Web UI
> * introduce common variable for bridge names in firewall simulator
> * update docs to reflect changes
> * add warning for interfaces named vmbrX that are not bridges
>
> 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
>
> pve-common:
>
> Stefan Hanreich (1):
> fix #545: interfaces: allow arbitrary bridge names in network config
>
> src/PVE/INotify.pm | 28 +++++++++++++++-------------
> 1 file changed, 15 insertions(+), 13 deletions(-)
>
>
> pve-docs:
>
> Stefan Hanreich (1):
> network: update specification for bridge names
>
> pve-network.adoc | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
>
> pve-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(-)
>
>
> pve-firewall:
>
> Stefan Hanreich (1):
> simulator: use new bridge naming scheme
>
> src/PVE/FirewallSimulator.pm | 29 +++++++++++++++++++----------
> src/PVE/Service/pve_firewall.pm | 5 +++--
> 2 files changed, 22 insertions(+), 12 deletions(-)
>
>
> proxmox-widget-toolkit:
>
> Stefan Hanreich (1):
> network: allow bridges to have any valid interface name
>
> src/Toolkit.js | 4 ++--
> src/node/NetworkEdit.js | 4 +++-
> 2 files changed, 5 insertions(+), 3 deletions(-)
>
>
> Summary over all repositories:
> 8 files changed, 60 insertions(+), 38 deletions(-)
>
applied series, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-04-21 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 8:07 [pve-devel] " Stefan Hanreich
2024-04-12 8:07 ` [pve-devel] [PATCH pve-common v4 1/6] fix #545: interfaces: allow arbitrary bridge names in network config Stefan Hanreich
2024-04-12 8:07 ` [pve-devel] [PATCH pve-docs v4 2/6] network: update specification for bridge names Stefan Hanreich
2024-04-12 8:07 ` [pve-devel] [PATCH pve-manager v4 3/6] sdn: qinq: vlan: properly validate bridge name Stefan Hanreich
2024-04-12 8:07 ` [pve-devel] [PATCH pve-manager v4 4/6] sdn: vlan: fix indentation in vlan edit dialogue Stefan Hanreich
2024-04-12 8:07 ` [pve-devel] [PATCH pve-firewall v4 5/6] simulator: use new bridge naming scheme Stefan Hanreich
2024-04-12 8:07 ` [pve-devel] [PATCH proxmox-widget-toolkit v4 6/6] network: allow bridges to have any valid interface name Stefan Hanreich
2024-04-21 12:19 ` Thomas Lamprecht [this message]
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=b5c3fdbb-2e61-40ee-b5db-3a8aa3534271@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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