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

["Alwin Antreich" <alwin@antreich.com>]

January 28, 2022 6:50 AM, "Thomas Lamprecht" <t.lamprecht@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?

@Aaron, or is it counter productive to what you try to do?

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

Cheers,
Alwin