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/4] evpn controller fix && cleanup
Date: Mon, 22 Jan 2024 11:59:05 +0100 [thread overview]
Message-ID: <15152a2f-9d73-4920-b859-36e2cf0d2f6c@proxmox.com> (raw)
In-Reply-To: <20231203154610.217714-1-aderumier@odiso.com>
Am 03/12/2023 um 16:46 schrieb Alexandre Derumier:
> This patch serie is fixing 1 critical bug with multiple exit-nodes
> and other minor ipv6 bug with prefix-list && null routes.
>
> Also cleaning the re-ordering of some values in frr.conf to match
> the output of frr running config.
>
> Alexandre Derumier (4):
> controllers: evpn: add ipv6 prefix-list support
> controllers: evpn: bugfix: use prefix-list in route-map instead evpn
> match
> controllers: evpn: frr config cleanup
> controllers: evpn: fix null routes order && ipv6
>
> src/PVE/Network/SDN/Controllers/EvpnPlugin.pm | 52 +++++++++++++++----
> .../expected_controller_config | 6 +--
> .../expected_controller_config | 6 +--
> .../evpn/ebgp/expected_controller_config | 6 +--
> .../ebgp_loopback/expected_controller_config | 6 +--
> .../evpn/exitnode/expected_controller_config | 19 ++++---
> .../expected_controller_config | 19 ++++---
> .../expected_controller_config | 18 +++++--
> .../exitnode_snat/expected_controller_config | 19 ++++---
> .../expected_controller_config | 33 +++++++++---
> .../exitnodenullroute/expected_sdn_interfaces | 8 +++
> .../zones/evpn/exitnodenullroute/sdn_config | 35 +++++++++++++
> .../evpn/ipv4/expected_controller_config | 6 +--
> .../evpn/ipv4ipv6/expected_controller_config | 6 +--
> .../expected_controller_config | 6 +--
> .../evpn/ipv6/expected_controller_config | 6 +--
> .../evpn/isis/expected_controller_config | 6 +--
> .../isis_loopback/expected_controller_config | 6 +--
> .../expected_controller_config | 6 +--
> .../multiplezones/expected_controller_config | 6 +--
> .../evpn/rt_import/expected_controller_config | 6 +--
> .../evpn/vxlanport/expected_controller_config | 6 +--
> 22 files changed, 203 insertions(+), 84 deletions(-)
>
sorry for the delay, applied series now, thanks!
prev parent reply other threads:[~2024-01-22 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 15:46 [pve-devel] " Alexandre Derumier
2023-12-03 15:46 ` [pve-devel] [PATCH pve-network 1/4] controllers: evpn: add ipv6 prefix-list support Alexandre Derumier
2023-12-03 15:46 ` [pve-devel] [PATCH pve-network 2/4] controllers: evpn: bugfix: use prefix-list in route-map instead evpn match Alexandre Derumier
2023-12-03 15:46 ` [pve-devel] [PATCH pve-network 3/4] controllers: evpn: frr config cleanup Alexandre Derumier
2023-12-03 15:46 ` [pve-devel] [PATCH pve-network 4/4] controllers: evpn: fix null routes order && ipv6 Alexandre Derumier
2024-01-06 6:41 ` [pve-devel] [PATCH pve-network 0/4] evpn controller fix && cleanup DERUMIER, Alexandre
2024-01-19 11:59 ` DERUMIER, Alexandre
2024-01-22 10:59 ` 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=15152a2f-9d73-4920-b859-36e2cf0d2f6c@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