public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [RFC qemu] block/gluster: do not warn about deprecation
Date: Mon, 2 Jun 2025 08:33:48 +0200	[thread overview]
Message-ID: <5ce6b740-f4e8-4d02-8554-5d4bd52e73df@proxmox.com> (raw)
In-Reply-To: <20250411093727.41474-1-f.ebner@proxmox.com>

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?
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?


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-06-02  6:33 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 [this message]
2025-06-02 10:51   ` Fiona Ebner

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=5ce6b740-f4e8-4d02-8554-5d4bd52e73df@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.ebner@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