From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 pve-network 0/3] zones: qinq : fix mutiples vnets/qinq zones
Date: Thu, 29 Apr 2021 13:17:56 +0200 [thread overview]
Message-ID: <20210429111759.231197-1-aderumier@odiso.com> (raw)
This fix bugs with qinq when vmbr0 is ovs or classic bridge,
when we define multiple vnets/qinq zones
changelog v2:
- fix typo in vlanaware test
Alexandre Derumier (3):
zones: qinq: ovs: fix duplicate ovs_ports with multiple zones/vnets
zones: qinq: classic bridge: fix bridge zone name with multiple
zones/vnets
zones: qinq: vlanaware bridge: add tests with multiple vnets/zones
PVE/Network/SDN/Zones/QinQPlugin.pm | 10 +++---
.../zones/qinq/bridge/expected_sdn_interfaces | 33 +++++++++++++++++--
test/zones/qinq/bridge/sdn_config | 7 +++-
.../bridge_vlanaware/expected_sdn_interfaces | 20 +++++++++++
test/zones/qinq/bridge_vlanaware/sdn_config | 7 +++-
.../expected_sdn_interfaces | 6 ++--
.../expected_sdn_interfaces | 6 ++--
test/zones/qinq/ovs/expected_sdn_interfaces | 28 +++++++++++++++-
test/zones/qinq/ovs/sdn_config | 7 +++-
9 files changed, 106 insertions(+), 18 deletions(-)
--
2.20.1
next reply other threads:[~2021-04-29 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 11:17 Alexandre Derumier [this message]
2021-04-29 11:17 ` [pve-devel] [PATCH v2 pve-network 1/3] zones: qinq: ovs: fix duplicate ovs_ports with multiple zones/vnets Alexandre Derumier
2021-04-29 11:17 ` [pve-devel] [PATCH v2 pve-network 2/3] zones: qinq: classic bridge: fix bridge zone name " Alexandre Derumier
2021-04-29 11:17 ` [pve-devel] [PATCH v2 pve-network 3/3] zones: qinq: vlanaware bridge: add tests with multiple vnets/zones Alexandre Derumier
2021-04-29 11:32 ` [pve-devel] applied-series: [PATCH v2 pve-network 0/3] zones: qinq : fix mutiples vnets/qinq zones Thomas Lamprecht
2021-04-29 12:22 ` aderumier
2021-04-29 12:46 ` 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=20210429111759.231197-1-aderumier@odiso.com \
--to=aderumier@odiso.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