From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 2/3] ceph pools create: enhance erasure-code description
Date: Tue, 3 May 2022 13:58:08 +0200 [thread overview]
Message-ID: <20220503115809.2566406-3-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20220503115809.2566406-1-a.lauterer@proxmox.com>
Mention which optional parameters will be used for the replicated
metadata pool but won't have an effect on the erasure coded data pool.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
PVE/API2/Ceph/Pools.pm | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/PVE/API2/Ceph/Pools.pm b/PVE/API2/Ceph/Pools.pm
index 9c3b8884..b0517a52 100644
--- a/PVE/API2/Ceph/Pools.pm
+++ b/PVE/API2/Ceph/Pools.pm
@@ -404,7 +404,9 @@ __PACKAGE__->register_method ({
},
'erasure-coding' => {
description => "Create an erasure coded pool for RBD with an"
- ." accompaning replicated pool for metadata storage.",
+ ." accompaning replicated pool for metadata storage."
+ ." The optional 'size', 'min_size' and 'crush_rule'"
+ ." parameters will be applied to the metadata pool.",
type => 'string',
format => $ec_format,
optional => 1,
--
2.30.2
next prev parent reply other threads:[~2022-05-03 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 11:58 [pve-devel] [PATCH manager/docs 0/3] EC follow ups Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH manager 1/3] ceph pools create: remove crush_rule for ec pool data Aaron Lauterer
2022-05-03 11:58 ` Aaron Lauterer [this message]
2022-05-03 11:58 ` [pve-devel] [PATCH docs 3/3] pveceph: ec pool: add note about parameter usage on creation Aaron Lauterer
2022-05-04 5:56 ` [pve-devel] applied: " Thomas Lamprecht
2022-05-04 5:56 ` [pve-devel] applied-series: [PATCH manager/docs 0/3] EC follow ups 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=20220503115809.2566406-3-a.lauterer@proxmox.com \
--to=a.lauterer@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