From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <a.lauterer@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 3FEFCBF32 for <pve-devel@lists.proxmox.com>; Fri, 8 Apr 2022 12:14:19 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 34F42D8ED for <pve-devel@lists.proxmox.com>; Fri, 8 Apr 2022 12:14:19 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id BA8D8D8B5 for <pve-devel@lists.proxmox.com>; Fri, 8 Apr 2022 12:14:17 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 8661345A14 for <pve-devel@lists.proxmox.com>; Fri, 8 Apr 2022 12:14:17 +0200 (CEST) From: Aaron Lauterer <a.lauterer@proxmox.com> To: pve-devel@lists.proxmox.com Date: Fri, 8 Apr 2022 12:14:12 +0200 Message-Id: <20220408101416.165312-1-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.029 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [RFC manager 0/4] Ceph add basic erasure code pool mgmt support X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 08 Apr 2022 10:14:19 -0000 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 -- 2.30.2