From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH storage,cluster,manager 0/13] multipath: cluster-wide config, storage and health overview
Date: Mon, 29 Jun 2026 15:20:24 +0200 [thread overview]
Message-ID: <s8oik71sctj.fsf@toolbox> (raw)
In-Reply-To: <20260626121000.2095591-1-t.lamprecht@proxmox.com> (Thomas Lamprecht's message of "Fri, 26 Jun 2026 14:07:30 +0200")
Thomas Lamprecht <t.lamprecht@proxmox.com> writes:
> This is a proof of concept for better multipath support in PVE. I talked it
> over with Friedrich back in May and put it together to get early feedback,
> also because there is other multipath and iSCSI work going on (for example
> Mira's storage mapping series).
>
> [ .. ]
>
> Open points:
>
> [ .. ]
>
> - Upgrade and adoption: PVE rewrites /etc/multipath/wwids to match its
> allow-list, so it drops WWIDs that PVE did not add, which is risky on nodes
> whose multipath was set up by hand or that boot from SAN. There is also no
> migration from an existing multipath.conf, and a no-touch guarantee for
> boot-from-SAN devices needs thought.
These patches correctly show the existing WWIDs and their status when
installed on a node with an existing /etc/multipath/wwids.
In my testing, the "rewrite" only happens after adding a new WWID using
the new API.
If an automatic upgrade path is not possible, would it be possible to
warn the user if /etc/multipath/wwids has entries and
/etc/pve/multipath.conf does not exist when adding a new WWID? Perhaps
this is enough for the user to do a proper migration.
--
Maximiliano
next prev parent reply other threads:[~2026-06-29 13:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 12:07 [PATCH storage,cluster,manager 0/13] multipath: cluster-wide config, storage and health overview Thomas Lamprecht
2026-06-26 12:07 ` [PATCH storage 01/13] multipath: add helper library and managed configuration Thomas Lamprecht
2026-06-26 14:43 ` Maximiliano Sandoval
2026-06-26 12:07 ` [PATCH storage 02/13] api: disks: add read-only multipath status endpoint Thomas Lamprecht
2026-06-26 12:07 ` [PATCH storage 03/13] api: multipath: add cluster-wide configuration endpoints Thomas Lamprecht
2026-06-26 12:07 ` [PATCH storage 04/13] multipath: add storage plugin for multipath LUNs Thomas Lamprecht
2026-06-26 12:07 ` [PATCH storage 05/13] lvm: allow a multipath storage as the base device Thomas Lamprecht
2026-06-26 12:07 ` [PATCH storage 06/13] multipath: broadcast per-node map health to the cluster KV store Thomas Lamprecht
2026-06-26 12:07 ` [PATCH storage 07/13] api: multipath: add cluster-wide health status endpoint Thomas Lamprecht
2026-06-26 12:07 ` [PATCH cluster 08/13] pmxcfs: track cluster-wide multipath configuration Thomas Lamprecht
2026-06-26 12:07 ` [PATCH manager 09/13] pvestatd: apply the cluster-wide multipath config on each node Thomas Lamprecht
2026-06-26 12:07 ` [PATCH manager 10/13] api: cluster: mount the multipath configuration endpoint Thomas Lamprecht
2026-06-26 12:07 ` [PATCH manager 11/13] pvestatd: broadcast multipath map health to the cluster Thomas Lamprecht
2026-06-26 12:07 ` [PATCH manager 12/13] ui: dc: add multipath health matrix and config editor Thomas Lamprecht
2026-06-26 14:05 ` Maximiliano Sandoval
2026-06-26 12:07 ` [PATCH manager 13/13] ui: node: show multipath maps and their paths under Disks Thomas Lamprecht
2026-06-29 13:20 ` Maximiliano Sandoval [this message]
2026-07-03 15:41 ` superseded: [PATCH storage,cluster,manager 0/13] multipath: cluster-wide config, storage and health overview Thomas Lamprecht
2026-07-03 16:12 ` Dietmar Maurer
2026-07-03 17:29 ` 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=s8oik71sctj.fsf@toolbox \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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.