From: "Alwin Antreich" <alwin@antreich.com>
To: "Aaron Lauterer" <a.lauterer@proxmox.com>,
"Thomas Lamprecht" <t.lamprecht@proxmox.com>,
"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH storage] rbd: add support for erasure coded ec pools
Date: Fri, 28 Jan 2022 10:54:43 +0000 [thread overview]
Message-ID: <29676a1a69dbb2be089f03d837f4f399@antreich.com> (raw)
In-Reply-To: <01a32358-484e-1c8b-61c9-e03b9df5dbae@proxmox.com>
January 28, 2022 10:50 AM, "Aaron Lauterer" <a.lauterer@proxmox.com> wrote:
> What exactly do you mean? How to add custom config options for external cluster
> (/etc/pve/priv/ceph/<storeid>.conf) and locally in the /etc/pve/ceph.conf AKA /etc/ceph/ceph.conf?
Oh. I was thinking, if the /etc/pve/priv/ceph/<storage>.conf is not favored, then I could document the usage of client settings in the /etc/pve/ceph.conf.
>
> Sure, AFAICS the custom <storeid>.conf has been added in 2016 [0]. I did a quick search in the
> admin guide and did not find anything about it.
>
> [0] https://git.proxmox.com/?p=pve-storage.git;a=commit;h=1341722
Then I'll prepare some docs patch. :)
> Right now, I am only working out the EC pools (data-pool) parameter. Having the current
> possibilities documented is surely a good idea.
>
> Out of curiosity, do you have to use the custom configs often?
So far it might have been a hand full of times. (that I recall)
Currently we have a small how-to on the website with the /etc/ceph.conf.[0] I want to update this guide as well.
Cheers,
Alwin
[0] https://croit.io/docs/master/hypervisors/proxmox
next prev parent reply other threads:[~2022-01-28 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 16:07 Aaron Lauterer
2022-01-26 18:30 ` Alwin Antreich
2022-01-27 11:27 ` Aaron Lauterer
2022-01-27 15:41 ` Alwin Antreich
2022-01-27 16:28 ` Aaron Lauterer
2022-01-28 5:50 ` Thomas Lamprecht
2022-01-28 9:22 ` Alwin Antreich
2022-01-28 9:50 ` Aaron Lauterer
2022-01-28 10:54 ` Alwin Antreich [this message]
2022-01-28 11:21 ` Aaron Lauterer
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=29676a1a69dbb2be089f03d837f4f399@antreich.com \
--to=alwin@antreich.com \
--cc=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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