From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v3 manager 0/2] rework ceph cfg api
Date: Mon, 20 Mar 2023 11:50:53 +0100 [thread overview]
Message-ID: <20230320105055.797165-1-a.lauterer@proxmox.com> (raw)
to avoid multiple configXXX endpoints for different things.
A new API endpoint is used: 'cfg' and the current 'config' and
'configdb' are moved there (first 2 patches). The result is
* cfg/
* raw (formerly config)
* db (formerly configdb)
The other patches from the previous series (adding a new key/value
endpoint and fixing #2515) are omitted as we can work on them later too.
changes since v2: some cleanup of unused imports
Aaron Lauterer (2):
api: ceph: add ceph/cfg path, deprecate ceph/config and ceph/configdb
ui: ceph config: use new ceph/cfg/ API endpoints
PVE/API2/Ceph.pm | 15 ++++-
PVE/API2/Ceph/Cfg.pm | 115 ++++++++++++++++++++++++++++++++++++
PVE/API2/Ceph/Makefile | 1 +
www/manager6/ceph/Config.js | 4 +-
4 files changed, 130 insertions(+), 5 deletions(-)
create mode 100644 PVE/API2/Ceph/Cfg.pm
--
2.30.2
next reply other threads:[~2023-03-20 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 10:50 Aaron Lauterer [this message]
2023-03-20 10:50 ` [pve-devel] [PATCH v3 manager 1/2] api: ceph: add ceph/cfg path, deprecate ceph/config and ceph/configdb Aaron Lauterer
2023-03-20 13:35 ` Dominik Csapak
2023-03-20 10:50 ` [pve-devel] [PATCH v3 manager 2/2] ui: ceph config: use new ceph/cfg/ API endpoints Aaron Lauterer
2023-03-20 13:36 ` [pve-devel] [PATCH v3 manager 0/2] rework ceph cfg api Dominik Csapak
2023-03-20 14:52 ` [pve-devel] applied-series: " 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=20230320105055.797165-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