From: Fiona Ebner <f.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC qemu] block/gluster: do not warn about deprecation
Date: Mon, 2 Jun 2025 12:51:15 +0200 [thread overview]
Message-ID: <54d75fc3-6f72-4ad0-8ef0-9d50ebb7e867@proxmox.com> (raw)
In-Reply-To: <5ce6b740-f4e8-4d02-8554-5d4bd52e73df@proxmox.com>
Am 02.06.25 um 08:33 schrieb Thomas Lamprecht:
> Am 11.04.25 um 11:37 schrieb Fiona Ebner:
>> Proxmox VE will not drop the GlusterFS plugin during the PVE 8.x
>> support lifecycle. Avoid scaring users early.
>
> Those warnings from QEMU come up as standard info in the task log IIRC?
Yes, exactly.
> I.e., not as task warning on our side. In that case, it might be nicer
> to just add a bit context, something like:
>
> ----8<----
> Native 'gluster' support will be deprecated and removed in Proxmox VE 9.
> Before upgrading to the next major version, you will need to switch to accessing your Gluster storage as directory storage or migrate to another storage type.
> ---->8----
>
> Or a shorter variant:
>
> ----8<----
> Native Gluster support will be removed in Proxmox VE 9.
> Before upgrading, switch to accessing Gluster as directory storage or migrate to a different storage type.
> ---->8----
>
> That might be less scaring while still conveying info to users that sooner
> or later need to do something about this–well, besides choosing to not upgrade
> ever. What do you think?
Ack, will send a v2!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-06-02 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 9:37 Fiona Ebner
2025-06-02 6:33 ` Thomas Lamprecht
2025-06-02 10:51 ` Fiona Ebner [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=54d75fc3-6f72-4ad0-8ef0-9d50ebb7e867@proxmox.com \
--to=f.ebner@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.