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. Anyhow, thanks to both of you for the constructive discussion, always appreciated. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel