[pve-devel] [PATCH manager 5/5] ceph pools: allow to create erasure code pools

[Aaron Lauterer]

On 4/28/22 16:32, Dominik Csapak wrote:
> is there a specific reason why you still force the autocreation
> of the storage? i don't mind really, but giving a reason
> would be nice. if there is no reason, i'd drop that since
> the user can specify it anyway and adding one manually
> should also not too hard..

I guess I could have been more explicit in the commit message. I decided to always create the storage config to have the coupling of ec pool and replicated metadata pool in place. We currently only have the RBD use case for EC pools in PVE itself and otherwise people might forget about it and any RBD image created without the data-pool parameter configured will be placed in the replicated pool.