From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH docs/network 0/2] improve behavior of frr service when pre-installed
Date: Tue, 8 Apr 2025 18:59:45 +0200 [thread overview]
Message-ID: <be1a6e52-34b8-45cb-aea7-af0c71c3223f@proxmox.com> (raw)
In-Reply-To: <20250408163250.355449-1-s.hanreich@proxmox.com>
We should also consider adding frr-pythontools to the ISO, since
otherwise applying doesn't work ootb.
On 4/8/25 18:32, Stefan Hanreich wrote:
> 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.
>
> pve-network:
>
> Stefan Hanreich (1):
> frr: enable frr service on reloading the controller config
>
> src/PVE/Network/SDN/Controllers/EvpnPlugin.pm | 1 +
> 1 file changed, 1 insertion(+)
>
>
> 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, 10 insertions(+), 12 deletions(-)
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-04-08 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 16:32 Stefan Hanreich
2025-04-08 16:32 ` [pve-devel] [PATCH pve-network 1/1] frr: enable frr service on reloading the controller config Stefan Hanreich
2025-04-08 18:43 ` Thomas Lamprecht
2025-04-08 19:39 ` Stefan Hanreich
2025-04-08 19:42 ` Stoiko Ivanov
2025-04-08 19:46 ` Stefan Hanreich
2025-04-08 16:32 ` [pve-devel] [PATCH pve-docs 1/1] sdn: frr update documentation for installing frr package Stefan Hanreich
2025-04-08 16:59 ` Stefan Hanreich [this message]
2025-04-08 17:07 ` [pve-devel] [PATCH docs/network 0/2] improve behavior of frr service when pre-installed Friedrich Weber
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=be1a6e52-34b8-45cb-aea7-af0c71c3223f@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