From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied: [PATCH pve-network 0/6] sdn multiples fixes
Date: Tue, 6 Jun 2023 10:42:03 +0200 [thread overview]
Message-ID: <32edfd57-b024-b518-fb99-18e458c41c55@proxmox.com> (raw)
In-Reply-To: <20230420213622.685809-1-aderumier@odiso.com>
Am 20/04/2023 um 23:36 schrieb Alexandre Derumier:
> This is a resend of the 4 last patches for pve-network
> + 2 new patches
>
>
> Alexandre Derumier (6):
> fix #4657 : evpn: fix exit-node with multiple vrf
> fix #4425: vxlan|evpn: add vxlan-port option
> fix #4662 : frr: fix config generation ordering
> fix #4389 : evpn: exit nodes : null routes subnets from other zones
> fix #4683 : zones: qinq: fix vlan-protocol with bridge vlan aware
> network reload: fix UPID parsing
>
> PVE/API2/Network/SDN.pm | 3 +-
> PVE/Network/SDN/Controllers/BgpPlugin.pm | 2 +-
> PVE/Network/SDN/Controllers/EvpnPlugin.pm | 83 ++++++++++------
> PVE/Network/SDN/Vnets.pm | 4 +-
> PVE/Network/SDN/Zones/EvpnPlugin.pm | 4 +
> PVE/Network/SDN/Zones/QinQPlugin.pm | 8 +-
> PVE/Network/SDN/Zones/VxlanPlugin.pm | 9 ++
> .../ebgp_loopback/expected_controller_config | 3 +-
> .../evpn/exitnode/expected_controller_config | 1 +
> .../expected_controller_config | 4 +-
> .../exitnode_snat/expected_controller_config | 1 +
> .../expected_controller_config | 98 +++++++++++++++++++
> .../exitnodenullroute/expected_sdn_interfaces | 81 +++++++++++++++
> test/zones/evpn/exitnodenullroute/interfaces | 7 ++
> test/zones/evpn/exitnodenullroute/sdn_config | 42 ++++++++
> .../multiplezones/expected_controller_config | 49 ++++++++++
> .../multiplezones/expected_sdn_interfaces | 81 +++++++++++++++
> test/zones/evpn/multiplezones/interfaces | 7 ++
> test/zones/evpn/multiplezones/sdn_config | 37 +++++++
> .../evpn/vxlanport/expected_controller_config | 41 ++++++++
> .../evpn/vxlanport/expected_sdn_interfaces | 44 +++++++++
> test/zones/evpn/vxlanport/interfaces | 7 ++
> test/zones/evpn/vxlanport/sdn_config | 26 +++++
> .../expected_sdn_interfaces | 4 +
> .../vxlan/vxlanport/expected_sdn_interfaces | 16 +++
> test/zones/vxlan/vxlanport/interfaces | 7 ++
> test/zones/vxlan/vxlanport/sdn_config | 11 +++
> 27 files changed, 640 insertions(+), 40 deletions(-)
> create mode 100644 test/zones/evpn/exitnodenullroute/expected_controller_config
> create mode 100644 test/zones/evpn/exitnodenullroute/expected_sdn_interfaces
> create mode 100644 test/zones/evpn/exitnodenullroute/interfaces
> create mode 100644 test/zones/evpn/exitnodenullroute/sdn_config
> create mode 100644 test/zones/evpn/multiplezones/expected_controller_config
> create mode 100644 test/zones/evpn/multiplezones/expected_sdn_interfaces
> create mode 100644 test/zones/evpn/multiplezones/interfaces
> create mode 100644 test/zones/evpn/multiplezones/sdn_config
> create mode 100644 test/zones/evpn/vxlanport/expected_controller_config
> create mode 100644 test/zones/evpn/vxlanport/expected_sdn_interfaces
> create mode 100644 test/zones/evpn/vxlanport/interfaces
> create mode 100644 test/zones/evpn/vxlanport/sdn_config
> create mode 100644 test/zones/vxlan/vxlanport/expected_sdn_interfaces
> create mode 100644 test/zones/vxlan/vxlanport/interfaces
> create mode 100644 test/zones/vxlan/vxlanport/sdn_config
>
applied, with `git am --directory=src <patches>`, as I separated packaging from source
recently, thanks!
ps. would be great to mock the access to CFS for the test system, otherwise building this
in isolated environments like via sbuild is broken (I just disabled tests there for now).
prev parent reply other threads:[~2023-06-06 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 21:36 [pve-devel] " Alexandre Derumier
2023-04-20 21:36 ` [pve-devel] [PATCH pve-network 1/6] fix #4657 : evpn: fix exit-node with multiple vrf Alexandre Derumier
2023-04-20 21:36 ` [pve-devel] [PATCH pve-network 2/6] fix #4425: vxlan|evpn: add vxlan-port option Alexandre Derumier
2023-04-20 21:36 ` [pve-devel] [PATCH pve-network 3/6] fix #4662 : frr: fix config generation ordering Alexandre Derumier
2023-04-20 21:36 ` [pve-devel] [PATCH pve-network 4/6] fix #4389 : evpn: exit nodes : null routes subnets from other zones Alexandre Derumier
2023-04-20 21:36 ` [pve-devel] [PATCH pve-network 5/6] fix #4683 : zones: qinq: fix vlan-protocol with bridge vlan aware Alexandre Derumier
2023-04-20 21:36 ` [pve-devel] [PATCH pve-network 6/6] network reload: fix UPID parsing Alexandre Derumier
2023-06-06 8:42 ` 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=32edfd57-b024-b518-fb99-18e458c41c55@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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