[pve-devel] [PATCH storage] rbd: add support for erasure coded ec pools

Aaron Lauterer a.lauterer at proxmox.com
Fri Jan 28 10:50:56 CET 2022

On 1/28/22 10:22, Alwin Antreich wrote:
> January 28, 2022 6:50 AM, "Thomas Lamprecht" <t.lamprecht at proxmox.com> wrote:
>> On 27.01.22 17:28, Aaron Lauterer wrote:
>>> Besides the whole "where to store the data-pool parameter" issue, having custom client configs per
>>> storage would most likely be its own feature request. Basically extending the current way to
>>> hyperconverged storages. Though that would mean some kind of config merging as the hyperconverged
>>> situation relies heavily on the default Ceph config file.
>>> I still see the custom config file as an option for the admin to add custom options, not to spread
>>> the PVE managed settings when it can be avoided.
>> Yeah config merging would be probably nicer if avoided, and we can add a
>> `ceph-opt` like format-string property that allows access to most of the
>> more relevant settings if demand comes up.
> K.
> Would you guys have any objection, when I send a docs patch to document the current client conf possibility, under /etc/pve/priv/ceph/<storage>.conf? Or rather document it for /etc/pve/ceph.conf?

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?

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
> @Aaron, or is it counter productive to what you try to do?

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?

>> Anyhow, thanks to both of you for the constructive discussion, always
>> appreciated.
> :)
> Cheers,
> Alwin

More information about the pve-devel mailing list