[pve-devel] [PATCH storage] rbd: add support for erasure coded ec pools
a.lauterer at proxmox.com
Fri Jan 28 12:21:41 CET 2022
On 1/28/22 11:54, Alwin Antreich wrote:
> January 28, 2022 10:50 AM, "Aaron Lauterer" <a.lauterer at 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.
Well, it is there for external clusters, just not really documented atm. For a hyperconverged cluster (no monhost line in the storage config, line 185 ) it is ignored .
If it is configured, it is then added as `-c` to the RBD command, therefore the default ceph config is ignored IIUC .
>> Sure, AFAICS the custom <storeid>.conf has been added in 2016 . I did a quick search in the
>> admin guide and did not find anything about it.
>>  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. I want to update this guide as well.
I took a quick look. JFYI the keyring (and cephfs secret) don't need to be placed manually anymore with recent versions as the pvesm command can take a path to those files and will place it at the correct location . GUI patches for that are currently reviewed.
Once this patch is applied, your guide will hopefully become a bit shorter. Or longer to cover both cases ;)
Have a great weekend!
>  https://croit.io/docs/master/hypervisors/proxmox
More information about the pve-devel