From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-network 0/1] evpn: update config to frr 8.5.1
Date: Tue, 23 May 2023 08:47:25 +0200 [thread overview]
Message-ID: <20230523064726.2298476-1-aderumier@odiso.com> (raw)
Hi,
This patch update evpn to frr 8.5.1 (for pve8)
This apply on top on my previous patch series (with a lot of fix, for pve7)
https://lists.proxmox.com/pipermail/pve-devel/2023-April/056619.html
Alexandre Derumier (1):
evpn: update config to frr 8.5.1
PVE/Network/SDN/Controllers/EvpnPlugin.pm | 7 ++++++-
.../evpn/advertise_subnets/expected_controller_config | 6 +++++-
.../disable_arp_nd_suppression/expected_controller_config | 6 +++++-
test/zones/evpn/ebgp/expected_controller_config | 6 +++++-
test/zones/evpn/ebgp_loopback/expected_controller_config | 6 +++++-
test/zones/evpn/exitnode/expected_controller_config | 6 +++++-
.../exitnode_local_routing/expected_controller_config | 6 +++++-
.../evpn/exitnode_primary/expected_controller_config | 6 +++++-
test/zones/evpn/exitnode_snat/expected_controller_config | 6 +++++-
.../evpn/exitnodenullroute/expected_controller_config | 8 +++++++-
test/zones/evpn/ipv4/expected_controller_config | 6 +++++-
test/zones/evpn/ipv4ipv6/expected_controller_config | 6 +++++-
.../evpn/ipv4ipv6nogateway/expected_controller_config | 6 +++++-
test/zones/evpn/ipv6/expected_controller_config | 6 +++++-
.../zones/evpn/multipath_relax/expected_controller_config | 6 +++++-
test/zones/evpn/multiplezones/expected_controller_config | 8 +++++++-
test/zones/evpn/rt_import/expected_controller_config | 6 +++++-
test/zones/evpn/vxlanport/expected_controller_config | 6 +++++-
18 files changed, 95 insertions(+), 18 deletions(-)
--
2.30.2
next reply other threads:[~2023-05-23 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 6:47 Alexandre Derumier [this message]
2023-05-23 6:47 ` [pve-devel] [PATCH pve-network 1/1] " Alexandre Derumier
2023-06-06 8:40 ` [pve-devel] applied: " 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=20230523064726.2298476-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.