From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-network 1/1] debian: migrate legacy mac/ipam db
Date: Tue, 19 Nov 2024 16:59:37 +0100 [thread overview]
Message-ID: <66e7c7ff-4c1c-4097-87d6-06c22e18b7d3@proxmox.com> (raw)
In-Reply-To: <20241119133056.167727-1-s.hanreich@proxmox.com>
Am 19.11.24 um 14:30 schrieb Stefan Hanreich:
> We opted for a simple copy of the legacy file to the new location,
> since any other migration path would be too strenuous. The worst-case
> scenario of failures with this approach is losing IPAM / MAC entries
> that are created during the update window in the legacy files by nodes
> that are not yet updated to the new version. Those can be fixed by
> a simple start / stop of the affected VMs, triggering a rewrite of the
> IPAM database.
>
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> ---
> I took the liberty of already including a version guard, since we will
> apply it directly before bumping. If that's a wrong assumption or if
> the version number is wrong, please adapt it respectively.
>
> debian/libpve-network-perl.postinst | 32 +++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 debian/libpve-network-perl.postinst
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-19 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 13:30 [pve-devel] " Stefan Hanreich
2024-11-19 15: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=66e7c7ff-4c1c-4097-87d6-06c22e18b7d3@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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