From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 82D0E1FF13C for ; Thu, 16 Apr 2026 06:09:10 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 500AA21099; Thu, 16 Apr 2026 06:09:10 +0200 (CEST) From: Kefu Chai 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 Message-ID: <20260416040829.313252-1-k.chai@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776312437551 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.337 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: EDM5WPY4DC7O7KQPO7V23LQM2BWRVVGE X-Message-ID-Hash: EDM5WPY4DC7O7KQPO7V23LQM2BWRVVGE X-MailFrom: k.chai@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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