public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC manager 0/4] Ceph add basic erasure code pool mgmt support
Date: Fri,  8 Apr 2022 12:14:12 +0200	[thread overview]
Message-ID: <20220408101416.165312-1-a.lauterer@proxmox.com> (raw)

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





             reply	other threads:[~2022-04-08 10:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 10:14 Aaron Lauterer [this message]
2022-04-08 10:14 ` [pve-devel] [PATCH manager 1/4] api: ceph: $get_storages check if data-pool too Aaron Lauterer
2022-04-08 10:14 ` [pve-devel] [RFC manager 2/4] pveceph: add management for erasure code rules Aaron Lauterer
2022-04-27 13:32   ` Dominik Csapak
2022-04-08 10:14 ` [pve-devel] [RFC manager 3/4] ceph tools: add check if erasure code profile exists Aaron Lauterer
2022-04-08 10:14 ` [pve-devel] [PATCH manager 4/4] ceph pools: allow to create erasure code pools Aaron Lauterer
2022-04-27 13:32   ` Dominik Csapak
2022-04-08 11:13 ` [pve-devel] [RFC manager 0/4] Ceph add basic erasure code pool mgmt support Aaron Lauterer
2022-04-27 13:37 ` Dominik Csapak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220408101416.165312-1-a.lauterer@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal