From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 1/3] ceph pools create: remove crush_rule for ec pool data
Date: Tue, 3 May 2022 13:58:07 +0200 [thread overview]
Message-ID: <20220503115809.2566406-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20220503115809.2566406-1-a.lauterer@proxmox.com>
The crush rule is an optional paramter which can be used for the
metadata pool, but the erasure coded data pool will always get its own
crush rule. Therefore this parameter can not be adapted.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
PVE/API2/Ceph/Pools.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/PVE/API2/Ceph/Pools.pm b/PVE/API2/Ceph/Pools.pm
index 70427277..9c3b8884 100644
--- a/PVE/API2/Ceph/Pools.pm
+++ b/PVE/API2/Ceph/Pools.pm
@@ -474,6 +474,7 @@ __PACKAGE__->register_method ({
$ec_data_param->{erasure_code_profile} = $ec->{profile};
delete $ec_data_param->{size};
delete $ec_data_param->{min_size};
+ delete $ec_data_param->{crush_rule};
# metadata pool should be ok with 32 PGs
$param->{pg_num} = 32;
--
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 ` Aaron Lauterer [this message]
2022-05-03 11:58 ` [pve-devel] [PATCH manager 2/3] ceph pools create: enhance erasure-code description Aaron Lauterer
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-2-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