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] [PATCH manager 0/5] Ceph add basic erasure code pool mgmt support
Date: Thu, 28 Apr 2022 13:58:04 +0200	[thread overview]
Message-ID: <20220428115809.1661165-1-a.lauterer@proxmox.com> (raw)

The first patch is one that we should have added when we added basic
support for ec pools [0].

The rest adds basic support to manage erasure coded (EC) pools. When
adding an EC pool we need to define how many k and m chunks we want for
the ec profile. Optionally one can define the failure domain and device
class.
Or if there is already another ec profile that should be used, it can be
specified as well.

Since EC pools need a replicated pool that will hold metadata, we follow
the same approach we already have for cephfs pools and have one metadata
and one data pool.
A few prerequisites were added to Ceph::Tools.

More details in the actual patches.


changes since rfc:

change the approach by handling ec profiles automatically on pool
creation and cleaning up ec profiles and crush rules on pool
desctruction. The whole ec profile mgmt CLI has been dropped for now.

Aaron Lauterer (5):
  api: ceph: $get_storages check if data-pool too
  ceph tools: add erasure code management functions
  ceph tools: add function to get pool properties
  ceph tools: add destroy crush rule destroy function
  ceph pools: allow to create erasure code pools

 PVE/API2/Ceph/Pools.pm | 129 ++++++++++++++++++++++++++++++++++++++---
 PVE/Ceph/Tools.pm      |  83 +++++++++++++++++++++++++-
 2 files changed, 201 insertions(+), 11 deletions(-)

-- 
2.30.2





             reply	other threads:[~2022-04-28 11:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 11:58 Aaron Lauterer [this message]
2022-04-28 11:58 ` [pve-devel] [PATCH manager 1/5] api: ceph: $get_storages check if data-pool too Aaron Lauterer
2022-04-28 11:58 ` [pve-devel] [PATCH manager 2/5] ceph tools: add erasure code management functions Aaron Lauterer
2022-04-28 14:19   ` Dominik Csapak
2022-04-28 11:58 ` [pve-devel] [PATCH manager 3/5] ceph tools: add function to get pool properties Aaron Lauterer
2022-04-28 14:20   ` Dominik Csapak
2022-04-28 11:58 ` [pve-devel] [PATCH manager 4/5] ceph tools: add destroy crush rule destroy function Aaron Lauterer
2022-04-28 11:58 ` [pve-devel] [PATCH manager 5/5] ceph pools: allow to create erasure code pools Aaron Lauterer
2022-04-28 14:32   ` Dominik Csapak
2022-04-29  7:33     ` Aaron Lauterer
2022-04-29  7:40       ` Thomas Lamprecht
2022-04-29  9:27         ` Aaron Lauterer
2022-04-28 18:31   ` [pve-devel] applied: " Thomas Lamprecht
2022-04-28 18:33 ` [pve-devel] applied: [PATCH manager 0/5] Ceph add basic erasure code pool mgmt support Thomas Lamprecht

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=20220428115809.1661165-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