From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 0/1] pveceph: document FastEC (allow_ec_optimizations)
Date: Thu, 16 Apr 2026 12:08:28 +0800 [thread overview]
Message-ID: <20260416040829.313252-1-k.chai@proxmox.com> (raw)
Ceph Tentacle's allow_ec_optimizations flag is a nice win for RBD-on-EC
workloads, though it's a one-way switch and the upstream code is still
settling in - seven post-release fixes landed in 20.2.1 (which we don't
ship yet).
I did think about adding a pveceph CLI flag or a web UI checkbox, but
pveceph doesn't expose other per-pool flags like compression_mode or
noscrub either, and operators are expected to use the Ceph CLI directly
for those. Treating allow_ec_optimizations as a special case felt
inconsistent. The web UI also doesn't have an EC pool creation form at
all, so a checkbox would need a much bigger UI change to have anywhere
to live.
So for now, just documenting it feels like the right call: what it does,
what the preconditions are, the one-way-switch caveat, and the Ceph CLI
commands to enable it. If the pattern for per-pool flags changes down the
road, pveceph can grow a knob then.
Kefu Chai (1):
pveceph: document FastEC (allow_ec_optimizations) on erasure coded
pools
pveceph.adoc | 104 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 104 insertions(+)
--
2.47.3
next reply other threads:[~2026-04-16 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 4:08 Kefu Chai [this message]
2026-04-16 4:08 ` [PATCH docs 1/1] pveceph: document FastEC (allow_ec_optimizations) on erasure coded pools Kefu Chai
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=20260416040829.313252-1-k.chai@proxmox.com \
--to=k.chai@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 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.