From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs/network v2 0/3] improve behavior of frr service when pre-installed
Date: Wed, 9 Apr 2025 00:15:11 +0200 [thread overview]
Message-ID: <20250408221514.61100-1-s.hanreich@proxmox.com> (raw)
Fixes the issue of the FRR service getting started, but not enabled when
applying an SDN configuration and updates the docs to reflect the new behavior.
Changes from v1 to v2:
* additionally fix the outfunc in the reload command, which caused a regression
with frr-pythontools 10.2.1
* move the enabled check before the invocation of frr-reload.py
pve-network:
Stefan Hanreich (2):
frr: remove erroneous outfunc from frr-reload command
frr: enable and start frr on reloading the controller config
src/PVE/Network/SDN/Controllers/EvpnPlugin.pm | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
pve-docs:
Stefan Hanreich (1):
sdn: frr update documentation for installing frr package
pvesdn.adoc | 21 +++++++++------------
1 file changed, 9 insertions(+), 12 deletions(-)
Summary over all repositories:
2 files changed, 13 insertions(+), 13 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-04-08 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 22:15 Stefan Hanreich [this message]
2025-04-08 22:15 ` [pve-devel] [PATCH pve-network v2 1/2] frr: remove erroneous outfunc from frr-reload command Stefan Hanreich
2025-04-08 22:15 ` [pve-devel] [PATCH pve-network v2 2/2] frr: enable and start frr on reloading the controller config Stefan Hanreich
2025-04-08 22:15 ` [pve-devel] [PATCH pve-docs v2 1/1] sdn: frr update documentation for installing frr package Stefan Hanreich
2025-04-09 6:21 ` [pve-devel] applied: [PATCH docs/network v2 0/3] improve behavior of frr service when pre-installed 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=20250408221514.61100-1-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal