From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Julien OHAYON <j.ohayon@xoxo.fr>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] OSPF when migrating from v8 to v9
Date: Wed, 8 Oct 2025 11:34:26 +0200 [thread overview]
Message-ID: <d6b0a647-71c5-43fc-8cf0-6b0f6fa9ec4e@proxmox.com> (raw)
In-Reply-To: <7B6E9EB5-6BFE-43FF-B44E-7CF030A938D0@xoxo.fr>
On 10/7/25 5:58 PM, Julien OHAYON wrote:
> Thanks for your reply. Unfortunately, when we apply the SDN configuration, it modifies the daemons file and sets it to “no”, since we haven’t configured OSPF directly in Proxmox. That’s the file I would like to prevent from being modified.
Ah sorry, I was only thinking of the upgrade process itself. In your
particular scenario (having an EVPN zone configured as well) I'm afraid
there's currently no easy way of preventing the daemons file from
getting overwritten by the SDN module.
The defaults are set in the frr config generation module [1] and
currently not overridable. I guess we'd have to expose a way of setting
the default value for those daemons to 1 instead of 0.
Another way would be trying to detect if the status of the daemons needs
to change compared to the previous SDN configuration and only re-write
the daemons file in the case it really *needs* to change instead of
every time. But that is probably a bit more tricky.
Could you open a feature request on our Bugzilla?
[1]
https://git.proxmox.com/?p=pve-network.git;a=blob;f=src/PVE/Network/SDN/Frr.pm;h=b607b32c248db1147b458fbfe3f32a94297d2c53;hb=HEAD#l117
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2025-10-08 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 6:16 Julien OHAYON
2025-10-07 13:52 ` Stefan Hanreich
2025-10-07 15:58 ` Julien OHAYON
2025-10-08 9:34 ` Stefan Hanreich [this message]
2025-10-08 10:48 ` Julien OHAYON
2025-10-08 18:24 ` Flavio Visentin via pve-user
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=d6b0a647-71c5-43fc-8cf0-6b0f6fa9ec4e@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=j.ohayon@xoxo.fr \
--cc=pve-user@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