all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH manager/docs 0/3] EC follow ups
Date: Wed, 4 May 2022 07:56:39 +0200	[thread overview]
Message-ID: <662bd86c-0753-142b-f66a-a5b4ec16d744@proxmox.com> (raw)
In-Reply-To: <20220503115809.2566406-1-a.lauterer@proxmox.com>

Am 5/3/22 um 13:58 schrieb Aaron Lauterer:
> Some small follow ups. Mainly adapting the docs and API descriptions to
> avoid misunderstandings.
> 
> Also removign the 'crush_rule' parameter for the EC pool upon creation
> as it gets its own crush rule anyway and we cannot change it.
> 
> manager: Aaron Lauterer (2):
>   ceph pools create: remove crush_rule for ec pool data
>   ceph pools create: enhance erasure-code description
> 
>  PVE/API2/Ceph/Pools.pm | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)

applied series, thanks!




      parent reply	other threads:[~2022-05-04  5:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 11:58 [pve-devel] " Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH manager 1/3] ceph pools create: remove crush_rule for ec pool data Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH manager 2/3] ceph pools create: enhance erasure-code description Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH docs 3/3] pveceph: ec pool: add note about parameter usage on creation Aaron Lauterer
2022-05-04  5:56   ` [pve-devel] applied: " Thomas Lamprecht
2022-05-04  5:56 ` Thomas Lamprecht [this message]

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=662bd86c-0753-142b-f66a-a5b4ec16d744@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal