From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager v5 0/3] Ceph OSD: add detail infos
Date: Mon, 12 Dec 2022 13:14:48 +0100 [thread overview]
Message-ID: <20221212121451.877054-1-a.lauterer@proxmox.com> (raw)
This patch series adds 2 new API endpoints for OSDs to fetch more
detailed information about a single OSD. One for overall information and
one for a single volume (block, db, wal).
More in the actual patches.
Series got [0]:
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
Tested-by: Dominik Csapak <d.csapak@proxmox.com>
Changes since v4:
api: call ceph-volume with the OSD id to avoid unnecessary work
Changes since v3:
- rebased
API (initially as follow up[1]):
- verify definedness of $pid and $memory after run_command.
also handle cast to int there and not in the assignment of
the return values. This way we get a `null` value returned in case we
never got any value.
Changes since v2:
drop widget-toolkit patch
implementing suggestions received on v2
rephrasing some error messages
renaming api return properties and grid columns in hopes to be clearer
Changes since v1:
squashed API commits into one
all new API endpoints are below {osdid} and {osdid} returns an index
incorporate other code improvements
Aaron Lauterer (3):
api ceph osd: add OSD index, metadata and lv-info
ui utils: add renderer for ceph osd addresses
ui: osd: add details window
Aaron Lauterer (3):
api ceph osd: add OSD index, metadata and lv-info
ui utils: add renderer for ceph osd addresses
ui: osd: add details window
PVE/API2/Ceph/OSD.pm | 324 ++++++++++++++++++++++++++++++++
www/manager6/Makefile | 1 +
www/manager6/Utils.js | 15 ++
www/manager6/ceph/OSD.js | 26 +++
www/manager6/ceph/OSDDetails.js | 280 +++++++++++++++++++++++++++
5 files changed, 646 insertions(+)
create mode 100644 www/manager6/ceph/OSDDetails.js
--
2.30.2
next reply other threads:[~2022-12-12 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 12:14 Aaron Lauterer [this message]
2022-12-12 12:14 ` [pve-devel] [PATCH manager v5 1/3] api ceph osd: add OSD index, metadata and lv-info Aaron Lauterer
2022-12-12 12:14 ` [pve-devel] [PATCH manager v5 2/3] ui utils: add renderer for ceph osd addresses Aaron Lauterer
2022-12-12 12:14 ` [pve-devel] [PATCH manager v5 3/3] ui: osd: add details window Aaron Lauterer
2023-02-08 10:00 ` [pve-devel] [PATCH manager v5 0/3] Ceph OSD: add detail infos Aaron Lauterer
2023-03-15 17:26 ` [pve-devel] applied: " 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=20221212121451.877054-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