public inbox for pve-devel@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>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] pveceph: add ecpool create wrapper for the CLI
Date: Fri, 29 Apr 2022 09:43:39 +0200	[thread overview]
Message-ID: <6d2195e4-5930-54ac-0190-e8bfd6c18e61@proxmox.com> (raw)
In-Reply-To: <20220429073930.727465-1-d.csapak@proxmox.com>

On 29.04.22 09:39, Dominik Csapak wrote:
> that exposes the ec options as seperate parameters instead of a format string
> (for convenience). I made the ceph_pool_common_options and ec_format
> public so that we can reuse them for that
> 
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> @Thomas, because you suggested something like that, but it seems a bit
> out of place to me, and giving the options as property-string is not too
> bad, e.g.
> 
> pveceph pool create poolname --erasure-coding k=2,m2
> 
> vs
> 
> pveceph ecpool create poolname 2 2


I mean, I'd have done:

pveceph ec-pool create poolname -k 2 -m 2

which is a bit more telling than using fixed options for k/m but anyhow, you may be
right in that the format string isn't to bad after all for the CLI too, and avoiding
extra commands can have its merits as it reduces complexity in some way too.

So its fine for me as is, minus the missing docs naturally ;-P




      reply	other threads:[~2022-04-29  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29  7:39 Dominik Csapak
2022-04-29  7:43 ` 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=6d2195e4-5930-54ac-0190-e8bfd6c18e61@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@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