One thing I forgot to mention is that due to quite a few $rados->mon_commands that are introduced here, there will be rebases needed when we apply the changes to librados2-perl. Similar to this patch [0] of that other series.
[0] https://lists.proxmox.com/pipermail/pve-devel/2022-March/052290.html On 4/8/22 12:14, Aaron Lauterer wrote:
This RFC series adds basic support to create erasure coded (EC) pools with the PVE tooling. We need to first manage EC profiles as they are the important part when someone wants to use EC pools. They define how the data is split up and how much coding/parity one wants. The actual creation of the EC pools follows the same approach we use for cephfs pools. One metadata and one EC coded data pool. More details in the actual patches. The first patch is one that we should have added when we added basic support for ec pools [0]. I sent it as RFC mainly to get some feedback, especially regarding the CLI interface for the profile management and if the approach on how to create EC pools, by adding an optional 'ecprofile' parameter to pool create, is one we are okay with from an interface POV. More details can be found in the individual patches. [0] https://git.proxmox.com/?p=pve-storage.git;a=commit;h=ef2afce74aba01f2ab698a5477f5e396fa4d3725 Aaron Lauterer (4): api: ceph: $get_storages check if data-pool too pveceph: add management for erasure code rules ceph tools: add check if erasure code profile exists ceph pools: allow to create erasure code pools PVE/API2/Ceph.pm | 6 + PVE/API2/Ceph/ECProfiles.pm | 249 ++++++++++++++++++++++++++++++++++++ PVE/API2/Ceph/Makefile | 1 + PVE/API2/Ceph/Pools.pm | 55 +++++++- PVE/CLI/pveceph.pm | 12 ++ PVE/Ceph/Tools.pm | 21 ++- 6 files changed, 335 insertions(+), 9 deletions(-) create mode 100644 PVE/API2/Ceph/ECProfiles.pm
_______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
