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: Re: [pve-devel] [PATCH v3 manager 0/3]fix 2515 use size defaults
Date: Thu, 15 Jun 2023 09:40:13 +0200	[thread overview]
Message-ID: <cd7289fb-20b1-71b5-4760-009a82ddb0c5@proxmox.com> (raw)
In-Reply-To: <20230411134018.1699848-1-a.lauterer@proxmox.com>

ping?

On 4/11/23 15:40, Aaron Lauterer wrote:
> The main goal of this series is to improve the handling of configured
> default size & min_size values when creating a new Ceph Pool in the GUI.
> 
> A new Ceph API endpoint, 'cfg/value', is added. It allows us to fetch
> values for config keys that are set either in the config DB of Ceph or
> in the ceph.conf file.
> 
> changes since v2:
> * API rework has been already applied
> * cleaned up JS code to set default values right where we get them from
>    the API instead of at multiple places in the CephPoolInputPanel
>    itself.
> 
> Aaron Lauterer (3):
>    api: ceph: add endpoint to fetch config keys
>    fix #2515: ui: ceph pool create: use configured defaults for size and
>      min_size
>    ui: ceph pool edit: rework with controller and formulas
> 
>   PVE/API2/Ceph/Cfg.pm      |  82 ++++++++++++++++++++++
>   www/manager6/ceph/Pool.js | 144 +++++++++++++++++++++++++++++---------
>   2 files changed, 191 insertions(+), 35 deletions(-)
> 




      parent reply	other threads:[~2023-06-15  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 13:40 Aaron Lauterer
2023-04-11 13:40 ` [pve-devel] [PATCH v3 manager 1/3] api: ceph: add endpoint to fetch config keys Aaron Lauterer
2023-04-11 13:40 ` [pve-devel] [PATCH v3 manager 2/3] fix #2515: ui: ceph pool create: use configured defaults for size and min_size Aaron Lauterer
2023-04-11 13:40 ` [pve-devel] [PATCH v3 manager 3/3] ui: ceph pool edit: rework with controller and formulas Aaron Lauterer
2023-06-15  7:40 ` Aaron Lauterer [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=cd7289fb-20b1-71b5-4760-009a82ddb0c5@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